You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into an issue using this library where my queries were timing out way earlier than the timeout I specified when defining the client. After debugging a bit I found that I am getting back a response code of 33333 when a query is still in flight. However, the current src/query.rs file seems to have QUERY_IN_PROGRESS_ASYNC_CODE set to 33334. After making this change things started working correctly. Since I'm never seeing the code 33334 come back I was wondering if you had seen it in your own testing, or if both of these codes need to be considered so that the library keeps polling for results.
I ran into an issue using this library where my queries were timing out way earlier than the timeout I specified when defining the client. After debugging a bit I found that I am getting back a response code of 33333 when a query is still in flight. However, the current src/query.rs file seems to have QUERY_IN_PROGRESS_ASYNC_CODE set to 33334. After making this change things started working correctly. Since I'm never seeing the code 33334 come back I was wondering if you had seen it in your own testing, or if both of these codes need to be considered so that the library keeps polling for results.
nickrobinson@0f01c7b
The text was updated successfully, but these errors were encountered: