-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Sharepoint Online] Invalid JSON will cause unactionable "generator didn't stop after athrow" errors #2309
Comments
We are seeing this too and it is preventing our connector from completing a full sync. The issue I see looks very similar to yours, but it does not stem from getting XML back. It looks like there is a payload error caused by a connection reset. Due to the long-running nature of our syncs, I think these happens somewhat frequently: Then, it looks like the retry wrapper is what's causing that It seems like a connectors/connectors/sources/sharepoint_online.py Lines 315 to 336 in 6952df2
Unfortunately, I'm not familiar enough with how this connector handles async retries or how Python generators in general work. |
@bean710 are you running connectors on-prem? Do you have a stack trace? Unfortunately, we don't have a Sharepoint Online instance that raises such errors, so we cannot reliably test fixes. It can help immensely if we test the bug fix together with you. |
@artem-shelkovnikov Yes, we are running the connector client on-prem and I have access to full logs with some additional logging I've added. I'll add the relevant stack trace below. I'd be happy to work with you in any way possible to get this resolved :) We've run into a few bugs, but I've "resolved" most of them and this is the one which is most consistently preventing our connector from completing a full sync.
|
Hi @artem-shelkovnikov, is there anything I can get to you to help resolve this? This is currently a blocker for us since although the issue is rare, our syncs are long-running which means we run into this regularly and are unable to complete a full sync. |
Hey @bean710, Sorry I did not get back to you - I've added a simple error ignore in the branch There's also some work in the meantime going on in this PR to add component to allow connectors ignore transient errors like this one. So let's test first if ignoring this specific error will help, if so I'll make a proper fix and merge. |
Hi @artem-shelkovnikov , it looks like I'm still getting that error related to the
|
Hi @bean710, I've pushed another fix to the same branch If it does not work, is it possible to share the response that you get from Sharepoint - specifically status code + body? |
We ran another full sync and are still seeing the same issue. I'm not seeing any response body, but the status code is 200. |
@bean710 is the stack trace the same? Can you share debug logs with all sensitive information wiped if you have any? |
Linking relevant issue from aiohttp aio-libs/aiohttp#4581 - maybe this will give us more insight into handling this edge case better for SPO. People also report that the connection being broken from the server side causes this. |
Bug Description
An error was reported with the following stacktrace:
Upon investigation it became clear, that this problem happens if resource returns invalid json on GET request, example test (assert is incorrect here, but this test will reproduce the error):
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Error is clearly communicated and printed to logs. Sync might continue, if it's non-critical error
The text was updated successfully, but these errors were encountered: