Thomas
08/26/2024, 6:21 PMCaused by: io.temporal.failure.ApplicationFailure: message='Server error : 500 Internal Server Error {"message":"Internal Server Error","logref":null,"path":null,"_links":{"self":{"href":"/api/v1/workload/create","templated":false,"profile":null,"deprecation":null,"title":null,"hreflang":null,"type":null,"name":null}},"_embedded":{"errors":[{"message":"Internal Server Error: Error executing PERSIST: ERROR: could not read block 8 in file \"base/16385/17447\": read only 0 of 8192 bytes","logref":null,"path":null,"_links":{},"_embedded":{}}]}}', type='io.airbyte.workload.api.client.generated.infrastructure.ServerException', nonRetryable=false
Would be happy if anyone had any idea what is causing this or how to troubleshoot. I haven't found anyone with a similar problem on Github issues.user
08/26/2024, 7:03 PMAn error occurred: Unexpected status code 401 from token endpoint
airbytehq/airbyteKRISHIV GUBBA
08/26/2024, 7:42 PMpayload = {
"data": "{"start":0,"max":999}",
"devKey": "xx",
"sessionId": "xx"
}
The "start" field represents the index of the first record that should be returned, and the "max" field is the maximum number of records that can be returned in the response. The highest value for this is 999.
I need to implement pagination, and I need the "start" field to be incremented by 999 to request a new page of records for every subsequent request until there are no more records left to be returned by the API.
MY ISSUE: How exactly can I increment the "start" field by 999, since it is nested within the payload? On top of this, the payload is sent to the API in form encoded format, and I'm not sure how to configure the YAML file in order to alter the nested "start" field for implementing the offset. Please help.
Here's the link to the API docs and the endpoint in question:
https://developer.bill.com/reference/ap-vendormgmt-listvendor
BILL API documentation
List vendors
List vendor objects. See Search operations with lists to learn about pagination, sorting, and filtering. Vendor address details are required for paying the vendor by check or for inviting the vendor to join the BILL network. Keep this information current at all times. nameOnCheck address1 addressCit...user
08/26/2024, 7:59 PMNaman Aggarwal
08/26/2024, 8:47 PMSean Miltenberger
08/26/2024, 9:02 PMJustin Beasley
08/26/2024, 10:03 PMcurl
from the same IP).k monish
08/27/2024, 6:17 AMAnthony LEBLEU
08/27/2024, 7:55 AMSyed Hamza Raza Kazmi
08/27/2024, 10:26 AMMichael Eaton
08/27/2024, 11:42 AMairbyte-ci
supported on macos running on Intel?
I have “successfully” installed it on my local machine…
michael@michaels-mbp-16 airbyte-master % make tools.airbyte-ci.install
Nothing to uninstall for pipelines :sleeping:
Uninstalled pipelines via pipx
Removing /Users/michael/.local/bin/airbyte-ci
Removed airbyte-ci
Removed airbyte-ci-internal
Removed airbyte-ci-dev
All airbyte-ci references removed from pyenv versions.
Cleanup of airbyte-ci install completed.
macOS based system detected.
Downloading from <https://connectors.airbyte.com/files/airbyte-ci/releases/macos/latest/airbyte-ci>
╔───────────────────────────────────────────────────────────────────────────────╗
│ │
│ AAA IIIII RRRRRR BBBBB YY YY TTTTTTT EEEEEEE CCCCC IIIII │
│ AAAAA III RR RR BB B YY YY TTT EE CC III │
│ AA AA III RRRRRR BBBBBB YYYYY TTT EEEEE _____ CC III │
│ AAAAAAA III RR RR BB BB YYY TTT EE CC III │
│ AA AA IIIII RR RR BBBBBB YYY TTT EEEEEEE CCCCC IIIII │
│ │
│ === Installation complete. v(latest)=== │
│ /Users/michael/.local/bin/airbyte-ci │
╚───────────────────────────────────────────────────────────────────────────────╝
Checking if airbyte-ci is correctly installed...
airbyte-ci is correctly installed at /Users/michael/.local/bin/airbyte-ci4
However, when I come to run it…
michael@michaels-mbp-16 airbyte-master % airbyte-ci
zsh: bad CPU type in executable: airbyte-ci
ThanksDanton Bertuol
08/27/2024, 12:12 PMThomas
08/27/2024, 12:55 PMBeatrice Nasike
08/27/2024, 3:57 PMAldo Orozco
08/27/2024, 4:14 PMWaiting on CHILD_PID 7
PARENT_PID: 1
the orchestrator pod shows a ton of these
2024-08-27 16:10:33 destination > INFO pool-3-thread-1 i.a.c.i.d.a.b.BufferManager(printQueueInfo):94 [ASYNC QUEUE INFO] Global: max: 768 MB, allocated: 10 MB (10.0 MB), %% used: 0.013020833333333334 | State Manager memory usage: Allocated: 10 MB, Used: 0 bytes, percentage Used 0.0
2024-08-27 16:10:33 destination > INFO pool-6-thread-1 i.a.c.i.d.a.FlushWorkers(printWorkerInfo):127 [ASYNC WORKER INFO] Pool queue size: 0, Active threads: 0
and the destination-bigquery-write shows something identical to the source
Waiting on CHILD_PID 7
PARENT_PID: 1
Any ideas?Alkis
08/27/2024, 6:28 PMairbyte_internal
schema. It doesn’t seem to be unpacking into the expected tables in the actual schema.
I’m using the default setup without any custom transformations or dbt, so I’m not sure what might be causing this. Has anyone else experienced this or know how to ensure the data is correctly unpacked into the final destination schema?
Thanks for any help you can provide!Henrique Melo
08/27/2024, 7:27 PMSean Miltenberger
08/27/2024, 8:11 PMAn unknown error occurred. (HTTP 504)
Jeremy Schroetter
08/28/2024, 12:07 AMKamal Tuteja
08/28/2024, 3:00 AMDean Lau
08/28/2024, 4:35 AMPortUnreachableException
, Port 80 can't be reached, anyone raised this before?
We are urging to use new version for Postgres Refresh & Retain featureAnil Pawar
08/28/2024, 7:55 AMuser
08/28/2024, 8:14 AMJulie Choong
08/28/2024, 8:57 AMpostgresql:
enabled: false
# Trying with "externalDatabase" and without "externalDatabase" makes no difference
externalDatabase:
host: "host-name"
user: "user-name"
database: "db-name"
password: "password-value"
port: 5432
jdbcUrl: "<postgresql://host-name:5432/db-name?ssl=true&sslmode=require>"
# trying "jdbc:<postgresql://host-name:5432/db-name?ssl=true&sslmode=require>" doesn't help either
global:
database:
host: "host-name"
user: "user-name"
database: "db-name"
password: "password-value"
port: 5432
sslmode: "require"
jdbcUrl: "<postgresql://host-name:25060/db-name?ssl=true&sslmode=require>"
Anil Pawar
08/28/2024, 9:22 AMuser
08/28/2024, 10:33 AMRytis Zolubas
08/28/2024, 1:41 PMunable to install airbyte chart: unable to install helm: pre-upgrade hooks failed: 1 error occurred:
* pod airbyte-abctl-airbyte-bootloader failed
it is pointing to an old airbyte pg databaseTom CAGNINACCI
08/28/2024, 3:05 PMFarman Pirzada
08/28/2024, 3:13 PMCaused by: org.postgresql.util.PSQLException: ERROR: cannot read from logical replication slot "airbyte_ratings_slot"
Detail: This slot has been invalidated because it exceeded the maximum reserved size.
The configuration for the LSN commit behavior is currently set to "While Reading Data". Could switching to "After Loading Data in the Destination" resolve the issue? It's not my airbyte instance so I don't have control of changing it. I do want to make sure I can advise the best course of action.