-
Notifications
You must be signed in to change notification settings - Fork 72
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
Investigate coordinator failure for faulty provider #1581
Comments
The reason is the I've created PR's that fix the issue: |
Hi @Siegrift, I'm not sure how to test this specific case, could you please advise? I understand I'd need a faulty provider but where to find/mock one? |
@metobom is periodically trying to reproduce the issue using 0.9.1 and the problematic provider. When he does, he will check if 0.9.2 still causes the same issue. Maybe skip testing this one. |
Hi @Siegrift, I've tested the issue. Steps: Deploy Airnode with a faulty provider URL (a Beeceptor URL with a 1000s delay before a response) I retested this now as I wiped earlier logs by mistake. |
@bbenligiray Just to clarify, I asked Martin to test this on master and leave the 0.9.2 for @metobom. Thanks @martinkolenic, this can be moved to DONE. |
https://api3workspace.slack.com/archives/C02AYRX8D89/p1669812538505089?thread_ts=1669715564.101439&cid=C02AYRX8D89
The text was updated successfully, but these errors were encountered: