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

Fix an issue with timeout on near rpc call #65

Closed
frolvanya opened this issue Jan 11, 2025 · 0 comments · Fixed by #64
Closed

Fix an issue with timeout on near rpc call #65

frolvanya opened this issue Jan 11, 2025 · 0 comments · Fixed by #64
Assignees
@frolvanya

Comments

@frolvanya
Copy link
Contributor

Right now, near-rpc-client's change_and_wait throws an error immediately upon getting timeout response. The expected behaviour should be waiting until either tx will reach an expected status (included/exectuted/final) or throw finalization error if waiting time was too long (e.g > DEFAULT_WAIT_FINAL_OUTCOME_TIMEOUT_SEC)
@frolvanya frolvanya self-assigned this Jan 11, 2025
@frolvanya frolvanya linked a pull request Jan 11, 2025 that will close this issue
fix: wait for request when timeout response is received #64
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@frolvanya frolvanya

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: wait for request when timeout response is received Near-One/bridge-sdk-rs
1 participant
@frolvanya