@kapa.ai Is it possible to restart airbyte launched by abctl?

@kapa.ai im getting error that the “Unable to start the source” - what docs shall i look?

@kapa.ai Trying to test a Postgres destination results in ‘An unknown error occurred. (HTTP 504)’ as the result. This seems to be the case regardless of what settings are used, and whether there’s even a server listening on the hostname

How to lower my wait time to the return of Zendesk Support? 2024-08-29 181604 replication-orchestrator > Records read: 400000 (176 MB) 511 2024-08-29 181611 replication-orchestrator > Records read: 405000 (178 MB) 512 2024-08-29 181615 source > Backing off _send(...) for 0.0s (airbyte_cdk.sources.streams.http.exceptions.UserDefinedBackoffException: Request URL: https://bhubhelp.zendesk.com/api/v2/incremental/organizations.json?start_time=1722470400, Response Code: 429, Response Text: {"errors":[{"code":"incremental-exports","title":"Number of allowed incremental export API requests per minute exceeded","status":429}]}) 513 2024-08-29 181615 source > Retrying. Sleeping for 45 seconds

@kapa.ai how do I enable api access for Airbyte OSS? There is no "Applications" entry under settings

@kapa.ai I'm using Otel as Airbyte metrics collector and it seems that all data for GSheets are coming as zero (running on version 0.51.1) , other integrations seems to be ok (Jira, Mongo and son ). Nothing in the open-telemetry logs colector nor in the airbyte metrics server

i get this error when i try to access airbyte from my private network “Backend service does not exist”

I am building a low-code sdk connection. How can I run it and just log the HTTP requests that are sent ?

Is here a way to clean up the airbyte postgres db, particularly to clean the old records in the attempts and history_node tables?

Is there anyway to specify the cron timezone when setting a schedule via the api?

I am getting value error sourceType ‘google-drive’ not found when trying to call the ‘create source’ API.

@kapa.ai how to configure postgres to use with airbyte without ssl ? Airbyte is complaining about │ sql schema version compatibility check failed: pq: SSL is not enabled on the server

@kapa.ai I need to use 2 different base url for the same connection on different streams. One is a search API that returns IDs the other is a data api which returns the data for the ids. Is this possible with the low code solution?

@kapa.ai I have an API that returns data like this. How do I select it using the low code selector: {

"status": 200,
  "body": [
    "100D",
    "1BQK",
    "1DP5",
    "1FL5",

@kapa.ai Our connection was working fine one 20 august but we paused it few days to manage our billing. The WAL increased quite a lot on our source database (status 'extended') without any lost because we do not purge WAL. Since yesterday, we are trying to unpause the connection but it is failing with the following error : "Socket is closed" We tried to increase the initial sync timeout to the maximum (2400) but it doesn't seems to help. Do you have any pro tips to make it works ?

when iam updating the source with correct credentials it is still throughing error like this An unknown error occurred. (HTTP 504)

I created my source with incorrect credentials...and when iam trying to delete that source why is it not allowing me to delete?

@kapa.ai I've been encountering an issue performing syncs in "Incremental | Append" mode from MSSQL sources, the tables get randomly completely re-loaded as if Airbyte cannot correctly evaluate the cursor on

LastUpdated

(with microsecond resolution but without timezone offset)

@kapa.ai what is hte most recent helm cart for Airbyte

Caused by: io.airbyte.workload.launcher.pods.KubeClientException: Destination pod failed to start within allotted timeout of 1145 seconds. (Timed out waiting for [1140000] milliseconds for [Pod] with name:[null] in namespace [airbyte].)

@kapa.ai how to add another stream in the existing pipeline that was not previously added

I have built a connector using no code connector builder and it has been to a workspace using Ui.. how to make it available across all workspaces

@kapa.ai I have installed abctl locally, mac m1. With the command abctl local install. But when I run the command abctl local credentials i do not get any credentials.

@kapa.ai is it possible to use abctl in my gke cluster?

@kapa.ai Is there a way to force airbyte to reperform the normalization from the _raw___stream_ into the output table?

how to configure local registry with abctl

@kapa.ai i'm getting this error when creating a manifest.yaml for a connector

ModelToComponentFactory.create_session_token_authenticator() missing 2 required positional arguments: 'name' and 'decoder'\n

@kapa.ai I've developed a custom connector that is running perfectly on airbyte: 0.50.7. I now want to upgrade airbyte from 0.50.7 to 0.59.1. My source is running perfectly while setting it up. When I want to connect to it with snowflake it fails during the select streams phase with this message: Discovering schema failed Failed to run schema discovery. and these logs: 2024-08-30 134858 platform > Cloud storage job log path: /workspace/f915a2fe-db5e-4df6-b1c6-45847c6acce2/0/logs.log

Yes, I can help with that. The 504 error you're encountering when trying to add your custom connector might be due to the image not being loaded into

kind

, which is used by

abctl

to manage Kubernetes in Docker. You can load your image into

kind

by running the following command:

bash kind load docker-image my-custom-connector:dev --name airbyte-abctl

Replace

my-custom-connector:dev

with the name and tag of your Docker image. After running this command, try adding your custom connector again. If you're still encountering issues, it might be helpful to view the logs of the specific pod that's causing the issue. You can do this with the following commands:

bash kubectl --kubeconfig ~/.airbyte/abctl/abctl.kubeconfig -n airbyte-abctl get pods kubectl --kubeconfig ~/.airbyte/abctl/abctl.kubeconfig -n airbyte-abctl logs [POD NAME]

Replace

[POD NAME]

with the name of the pod you're interested in. These commands will help you identify any issues that might be occurring within the pod. If you're still encountering issues after trying these steps, please provide more detailed logs so we can further assist you. For more information, you can refer to this [Github Issue](https://github.com/airbytehq/airbyte/issues/43893) where a similar problem was discussed.

This message was deleted.