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

re:dash should not lose query output when client connection drops #36

Closed
fbertsch opened this issue Feb 6, 2017 · 0 comments
Closed

re:dash should not lose query output when client connection drops #36

fbertsch opened this issue Feb 6, 2017 · 0 comments

Comments

@fbertsch
Copy link

fbertsch commented Feb 6, 2017

Currently, if a client connection drops, re:dash errors with something akin to "lost connection" (I don't remember what it was exactly). But the query is still running, and the web server can still connect to it and get the result. Why not treat these just like scheduled queries, and load the result on the query page no matter what the client does (unless they cancel)? Then when I reconnect, I can see the result, even if my connection dropped.
@washort washort closed this as completed Feb 16, 2017
washort pushed a commit that referenced this issue Feb 22, 2017
Retry fetching query result on failure (fixes #36)
ee74ffd
washort pushed a commit that referenced this issue Mar 9, 2017
Retry fetching query result on failure (fixes #36)
0647647
washort pushed a commit that referenced this issue Mar 22, 2017
Retry fetching query result on failure (fixes #36)
db9f4f4
washort pushed a commit that referenced this issue Apr 6, 2017
Retry fetching query result on failure (fixes #36)
b557740
washort pushed a commit that referenced this issue Dec 12, 2017
Retry fetching query result on failure (fixes #36)
3f0118b
washort pushed a commit that referenced this issue Dec 12, 2017
Retry fetching query result on failure (fixes #36)
2dbe0ad
washort pushed a commit that referenced this issue Dec 13, 2017
Retry fetching query result on failure (fixes #36)
b1ff3f4
washort pushed a commit that referenced this issue Jan 8, 2018
Retry fetching query result on failure (fixes #36)
60563fe
washort pushed a commit that referenced this issue Jan 17, 2018
Retry fetching query result on failure (fixes #36)
31ea3b5
washort pushed a commit that referenced this issue Feb 6, 2018
Retry fetching query result on failure (fixes #36)
0e2cb6f
washort pushed a commit that referenced this issue Feb 28, 2018
Retry fetching query result on failure (fixes #36)
cf5dbe0
jezdez pushed a commit that referenced this issue Mar 5, 2018
@jezdez
Retry fetching query result on failure (fixes #36)
b4a8d5c
emtwo pushed a commit that referenced this issue May 25, 2018
Retry fetching query result on failure (fixes #36)
997ceea
washort pushed a commit that referenced this issue Jul 25, 2018
Retry fetching query result on failure (fixes #36)
545d9bd
jezdez pushed a commit that referenced this issue Aug 16, 2018
@jezdez
Retry fetching query result on failure (fixes #36)
8f9e63d
jezdez pushed a commit that referenced this issue Sep 6, 2018
@jezdez
Retry fetching query result on failure (fixes #36)
a212d1e
@jezdez jezdez mentioned this issue Sep 14, 2018
Closed
jezdez pushed a commit that referenced this issue Nov 1, 2018
@jezdez
Retry fetching query result on failure (fixes #36)
6cbd4cc
@snyk-bot snyk-bot mentioned this issue Aug 17, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fbertsch