poornima Venkatesha
09/05/2024, 12:14 PMJaydan Pratts
09/05/2024, 12:20 PMForTest App
09/05/2024, 12:40 PMJames N
09/05/2024, 12:43 PMJaydan Pratts
09/05/2024, 1:02 PM/app/connector_acceptance_test/tests/test_core.py:624: AssertionError
------------------------------ Captured log setup ------------------------------
WARNING root:conftest.py:137 Connector config file not found at /test_input/secrets/config.json
where should I be placing my config.json for acceptance testing, and what should it contain?Khushbu Adav
09/05/2024, 1:02 PM2024-09-05 12:53:35 source > During the sync, the following streams did not sync successfully: custom_collections: AirbyteTracedException("'message'")
2024-09-05 12:53:35 INFO i.a.w.i.VersionedAirbyteStreamFactory(internalLog):326 - During the sync, the following streams did not sync successfully: custom_collections: AirbyteTracedException("'message'")
2024-09-05 12:53:35 source > None
what is the issue?kapa.ai
09/05/2024, 1:33 PM/manifest.json
and forbidden access (403 error) to /api/v1/users/get
when using Airbyte behind an NGINX reverse proxy. The 401 Unauthorized error typically indicates that the request lacks valid authentication credentials for the target resource. In this case, it seems to be related to the /manifest.json
file. The 403 Forbidden error, on the other hand, indicates that the server understood the request, but it refuses to authorize it. This status is similar to 401 (Unauthorized), but indicates that the client must authenticate itself to get the requested response. In this case, it seems to be related to the /api/v1/users/get
endpoint. Unfortunately, the provided knowledge sources do not contain specific solutions to these issues. However, they do suggest that other users have experienced similar issues when using Airbyte with a reverse proxy. One user managed to get it working on port 8000 with insecure-cookies and without reverse proxy by using the abctl local install --no-browser --insecure-cookies --host <http://xxx-vm-airbyte-04.westeurope.cloudapp.azure.com|xxx-vm-airbyte-04.westeurope.cloudapp.azure.com>
command and setting the email and organization. They were then able to log in via the credentials provided by abctl local credentials
[source](https://github.com/airbytehq/airbyte/issues/44198). It's recommended to check your NGINX configuration and ensure that it's correctly set up to proxy requests to Airbyte. Also, ensure that your Airbyte instance is correctly configured to accept connections from your NGINX server. If the issue persists, it would be beneficial to reach out to the Airbyte community or support for more specific guidance.kapa.ai
09/05/2024, 1:33 PM/manifest.json
and /api/v1/users/get
. The 401 Unauthorized error on /manifest.json
suggests that the server is rejecting your request due to invalid credentials. This could be due to incorrect configuration of your NGINX reverse proxy or issues with your Airbyte setup. The 403 Forbidden error on /api/v1/users/get
indicates that the server understood the request, but it refuses to authorize it. This status is similar to 401 (Unauthorized), but indicates that authentication alone will not suffice - i.e., the client must authenticate itself to get the requested response. Unfortunately, the provided knowledge sources do not contain a specific solution to these issues. However, you might want to check your NGINX and Airbyte configurations, ensure that you're using the correct credentials, and that your reverse proxy is correctly set up to forward requests to Airbyte. For more detailed help, consider reaching out to the Airbyte community on their [discussion forum](https://discuss.airbyte.io/) or opening an issue on their [Github page](https://github.com/airbytehq/airbyte/issues). Sources: - [Forum Post: NGINX reverse proxy behind port forward to local Airbyte webserver](https://discuss.airbyte.io/t/2429) - [Github Issue (closed): Can't get passed Getting Started screen after fresh installation](https://github.com/airbytehq/airbyte/issues/44198) - [Airbyte Public API - Connections](https://reference.airbyte.com/reference/start)Andrei Delcea
09/05/2024, 1:35 PMGabriele Cacchioni
09/05/2024, 1:36 PMAndrei Delcea
09/05/2024, 1:40 PMAndrei Delcea
09/05/2024, 1:42 PMJoseph To
09/05/2024, 1:47 PMAbhra Gupta
09/05/2024, 1:54 PMAndrei Delcea
09/05/2024, 1:57 PMJoseph To
09/05/2024, 2:03 PMJoseph To
09/05/2024, 2:09 PMJoseph To
09/05/2024, 2:12 PMio.temporal.failure.ActivityFailure: Activity with activityType='RunWithWorkload' failed: 'Activity task failed'. scheduledEventId=12, startedEventId=13, activityId=8e96f207-a7c7-3d04-bef3-d50835de703b, identity='1@airbyte-064-worker-5585fcbd5d-5js9l', retryState=RETRY_STATE_MAXIMUM_ATTEMPTS_REACHE
Torsten Fraust
09/05/2024, 2:16 PMFailure executing: PATCH at: <https://10.96.0.1:443/api/v1/namespaces/airbyte-abctl/pods/on-snowflake-check-ccb57db5-d34d-4dd0-8521-9b0be39fb524-0-aornd?fieldManager=fabric8>.
Andrei Delcea
09/05/2024, 2:47 PMDaniel Holleran
09/05/2024, 3:08 PMJoseph To
09/05/2024, 3:18 PMTorsten Fraust
09/05/2024, 3:38 PMJonathan Golden
09/05/2024, 3:42 PMJehkindra Klu-Jackson
09/05/2024, 3:52 PMLuis Alfonso
09/05/2024, 4:14 PM2024-09-04 23:39:41 source > INFO pool-3-thread-1 i.a.c.i.d.AirbyteDebeziumHandler$CapacityReportingBlockingQueue(reportQueueUtilization):48 CDC events queue stats: size=0, cap=10000, puts=45, polls=0
1881
2024-09-04 23:39:41 source > INFO main i.a.c.i.d.i.DebeziumRecordIterator(computeNext):87 CDC events queue poll(): blocked for PT10.522826179S after its previous call which was also logged.
1882
2024-09-04 23:39:41 source > INFO main i.a.c.i.d.i.DebeziumRecordIterator(computeNext):140 CDC events queue poll(): returned a heartbeat event: no progress since last heartbeat.
1883
2024-09-04 23:39:52 source > INFO pool-3-thread-1 i.a.c.i.d.AirbyteDebeziumHandler$CapacityReportingBlockingQueue(reportQueueUtilization):48 CDC events queue stats: size=0, cap=10000, puts=46, polls=0
1884
2024-09-04 23:39:52 source > INFO main i.a.c.i.d.i.DebeziumRecordIterator(computeNext):87 CDC events queue poll(): blocked for PT10.52142362S after its previous call which was also logged.
1885
2024-09-04 23:39:52 source > INFO main i.a.c.i.d.i.DebeziumRecordIterator(computeNext):140 CDC events queue poll(): returned a heartbeat event: no progress since last heartbeat.
1886
2024-09-04 23:40:02 source > INFO pool-3-thread-1 i.a.c.i.d.AirbyteDebeziumHandler$CapacityReportingBlockingQueue(reportQueueUtilization):48 CDC events queue stats: size=0, cap=10000, puts=47, polls=0
1887
Torsten Fraust
09/05/2024, 4:15 PMparrent stream
- incremental Parent
states this: "Incremental Parent
Causes the parent stream's records to be read incrementally, so only parent records that have been updated since the last sync will be retrieved for use in this stream.
This only works if this child stream is Incremental.
WARNING: If the parent stream records' cursor fields are NOT updated whenever the relevant child records are updated, then those child records may be missed!"
Why is this only working if the child stream is incremental? The api for the child stream only accepts one imput which is the id form the parent stream. Is it even possible to make the child steam incremental if the api is not accepting a date filter for the child stream?kapa.ai
09/05/2024, 4:42 PMbash sudo add-apt-repository ppa:deadsnakes/ppa sudo apt update apt list | grep python3.10 sudo apt install python3.10 sudo apt install python3.10-distutils curl <https://bootstrap.pypa.io/get-pip.py> -o get-pip.py sudo python3.10 get-pip.py sudo apt install python3.10-venv
In addition, Python 3.10 or later is also a prerequisite for several Airbyte tutorials, such as the [Outdoor Activity Analytics Stack with Airbyte, dbt, Dagster and BigQuery](https://airbyte.com/tutorials/outdoor-activity-analytics-stack-with-airbyte-dbt-dagster-and-bigquery) and the [End-to-end RAG using Airbyte Cloud, S3, BigQuery and Pinecone](https://airbyte.com/tutorials/end-to-end-rag-using-airbyte-cloud-s3-bigquery-and-pinecone). If you haven't installed Python 3.10 or later yet, you can download and install it from [Python's official website](https://www.python.org/downloads/).Curtis
09/05/2024, 5:16 PMglobal:
deploymentMode: "oss"
edition: "community"
env_vars:
HTTP_IDLE_TIMEOUT: 1800s
webapp:
ingress:
annotations:
<http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>: internal
<http://nginx.ingress.kubernetes.io/proxy-body-size|nginx.ingress.kubernetes.io/proxy-body-size>: 16m
<http://nginx.ingress.kubernetes.io/proxy-send-timeout|nginx.ingress.kubernetes.io/proxy-send-timeout>: 1800
<http://nginx.ingress.kubernetes.io/proxy-read-timeout|nginx.ingress.kubernetes.io/proxy-read-timeout>: 1800
I'm starting airbyte like this: abctl local install --values <path_to_config_file>
Any idea how I might troubleshoot/fix this?Vadym Maltsev
09/05/2024, 5:20 PM