Natalie
Justin Beasley
07/26/2024, 7:21 PMThe progress of active syncs is now reported every 10 seconds for increased visibility and tracking (available in OSS v.0.63.5). . . one thing I wanted to point out is that since the addition of the update interval on active syncs, we've noticed an increase in the number of HTTP 500 errors we see when working in the UI and having these pages on screen. It seems like these just happen occasionally (maybe related to the auth proxy Airbyte sits behind? not sure if everyone is seeing these), but with more requests being sent it comes up more often . . . it may be good for these background checks to be treated more opportunistically and not trigger UI errors (at least not until it hits some threshold of missed requests, e.g. 3 or 6) to help avoid transient errors that users likely wouldn't even notice otherwise. Just an idea that might help reduce user-impacting error noise 🙂
Chandler Prall (Airbyte)
07/29/2024, 1:44 PMit may be good for these background checks to be treated more opportunistically and not trigger UI errors (at least not until it hits some threshold of missed requests, e.g. 3 or 6) to help avoid transient errors that users likely wouldn't even notice otherwise.Great thing to note, I'll make sure its discussed in our frontend sync. I'm seeing ~10/day error responses for this endpoint, so not a huge increase but definitely something to watch. There are some other background calls we make to keep page data fresh, (and also error at times) and we should find a way to keep them from crashing the page.
Tim Roes (Airbyte)
08/01/2024, 1:22 PMJustin Beasley
08/01/2024, 1:24 PMTim Roes (Airbyte)
08/01/2024, 1:25 PMJustin Beasley
08/02/2024, 3:05 PM{
"url": "https://[REDACTED]/workspaces/1ad4ae36-9516-4549-9a2b-b161029b4411/connections/29344389-b2bb-43a1-9fff-abfbbccf4833/replication",
"airbyteVersion": "0.63.13",
"errorType": "HttpError",
"errorConstructor": "Th",
"error": {
"i18nKey": "errors.http.internalServerError",
"i18nParams": {
"status": 500
},
"name": "HttpError",
"requestId": "kAGoJSntvmMeXXm5s9qhQN",
"request": {
"url": "/api/v1/actor_definition_versions/get_for_destination",
"method": "post",
"headers": {
"Content-Type": "application/json"
},
"data": {
"destinationId": "02e9b259-639f-44f6-9732-e1a889d6ee2a"
}
},
"status": 500,
"response": "An internal server error occurred."
},
"stacktrace": "HttpError: errors.http.internalServerError\n at Vpe (https://[REDACTED]/assets/core-lx5fw6bdzu.js:119:9851)",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36",
"featureFlags": {}
}
Not particularly helpful there.
This one wasn't the endpoint I normally see, so I'll keep an eye out for another. But it did pop up on a sync screen sitting idle, so I'm guessing it was still a background request of some type.Tim Roes (Airbyte)
08/02/2024, 3:07 PMresponse but it's a plain string, this feels like it's not coming from the airbyte server even, but is caused by something else within the infrastructure?Justin Beasley
08/02/2024, 3:10 PMTim Roes (Airbyte)
08/02/2024, 3:12 PMJustin Beasley
08/02/2024, 3:35 PMTim Roes (Airbyte)
08/02/2024, 3:54 PMTim Roes (Airbyte)
08/02/2024, 3:56 PM