Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Queries timing out on device first/cold boot #1471

Open
AshishKumarD opened this issue Dec 3, 2024 · 7 comments
Open

Queries timing out on device first/cold boot #1471

AshishKumarD opened this issue Dec 3, 2024 · 7 comments
Labels
Priority: Waiting to be assigned To be inside the next release process, it need to be marked with some level of priority PRs encouraged PRs are welcome if stakeholders want to take ownership

Comments

@AshishKumarD
Copy link

AshishKumarD commented Dec 3, 2024 •
edited
Loading

When the device is first booted up the queries seem to randomly fail and timeout.
@IraDolynska
Copy link

same issue. I am randomly getting TimeoutException after 0:00:05.000000: No stream event error

@vincenzopalazzo
Copy link
Collaborator

what version are you running? please if you are not running the beta run it

@AshishKumarD
Copy link
Author

what version are you running? please if you are not running the beta run it

Running beta-9. Tried to recreate the issue but it's random. The only pattern I noticed is it happens during Cold Boot/ Device Boot up.

@vincenzopalazzo
Copy link
Collaborator

Mh strange, no idea how to reproduce it

@vincenzopalazzo vincenzopalazzo added PRs encouraged PRs are welcome if stakeholders want to take ownership Priority: Waiting to be assigned To be inside the next release process, it need to be marked with some level of priority labels Dec 6, 2024
@wcoder
Copy link

wcoder commented Dec 9, 2024

same issue:

macOS -> android-x64 emulator API 34

  • flutter: 3.24.5
  • graphql_flutter: 5.2.0-beta.7
    • graphql: 5.2.0-beta.9

@wcoder
Copy link

wcoder commented Dec 10, 2024 •
edited
Loading

ref: #1457

Workaround:

graphql_flutter: ^5.2.0-beta.7
graphql: 5.2.0-beta.8

randomly fail and timeout.

because sometimes your backend returns results in longer than 5 sec.

@titobrezende
Copy link

we should have a parameter to control the desired timeout

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority: Waiting to be assigned To be inside the next release process, it need to be marked with some level of priority PRs encouraged PRs are welcome if stakeholders want to take ownership
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@wcoder @titobrezende @vincenzopalazzo @IraDolynska @AshishKumarD