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.

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

do not retry ExitErrors in ui.retryStep #5668

Merged
merged 1 commit into from
Nov 25, 2024
Merged

Conversation

hughy
Copy link
Contributor

@hughy hughy commented Nov 22, 2024

Summary

if the command is exiting due to user action (e.g., choosing not to continue) or an un-retryable problem then we should not prompt to retry

Testing Plan

manual testing:
try to sign a transaction with ledger device locked. when prompted to unlock device and retry choose 'Cancel'

before:
image

after:
image

Documentation

Does this change require any updates to the Iron Fish Docs (ex. the RPC API
Reference
)? If yes, link a
related documentation pull request for the website.

[ ] Yes

Breaking Change

Is this a breaking change? If yes, add notes below on why this is breaking and label it with breaking-change-rpc or breaking-change-sdk.

[ ] Yes

@hughy hughy requested a review from a team as a code owner November 22, 2024 20:48
if the command is exiting due to user action (e.g., choosing not to continue)
or an un-retryable problem then we should not prompt to retry
@hughy hughy force-pushed the feat/hughy/retry-exit-error branch from f9a6833 to 0041221 Compare November 22, 2024 20:49
Copy link
Contributor

@NullSoldier NullSoldier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested manually, looks good.

@hughy hughy merged commit 6bdd3ec into staging Nov 25, 2024
12 checks passed
@hughy hughy deleted the feat/hughy/retry-exit-error branch November 25, 2024 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants