-
Notifications
You must be signed in to change notification settings - Fork 21
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
Partially completed query state not captured by SDK #124
Comments
@bh2smith is this on the roadmap? I ran into some issues with this missing state |
I am sure it will be done at some point, although I don't have capacity for this at the moment. Maybe @waddahAldrobi? We also welcome community contributions! |
Hey guys, I faced the
|
Oh... so your "run_query" is failing because its a long running query and we are unable to parse the type so it fails! If this is a major blocker we can include the new query execution state without actually making use of it (so the program doesn't crash because of a parse error). I opened a PR #125. If this is blocking your complex query from running (i.e. crashing the program), let me know and I can get a hot-fix out ASAP. |
I've added a note internally to document this. |
So then partial would also constitute a terminal state. I can add that to the PR logic. |
Yes, that's exactly right together with @RichardKeo 's comment. I am getting some transaction hashes for a bit of a long period using the API. I was thinking I would get partial results similar to using the UI. It's right now a blocker. Well can be considered a warning as well indicating I need to tighten my limits. |
I feel like it should be similar to the UI. Let's get the output out and show a warning this is a partial result. Is that what you mean as well? |
hey folks any update on this issue? this is a major blocker for us |
Over here we don't have the query state
QUERY_STATE_COMPLETED_PARTIAL
.May be related to #118 (allow partial flag).
The text was updated successfully, but these errors were encountered: