-
Notifications
You must be signed in to change notification settings - Fork 82
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
soroban-cli bump outputs an error while successful #969
Comments
The issue is here
The transaction is successful but the updated expiration is missing. |
I suspect that the bump operation is a noop but that the CLI expects a change in the transaction metadata. @vinamogit apart from confirming that the expiration changed, did you also confirm that the expiration of the entry changed? Do you also have the transaction's hash hanging around? |
Can confirm that this is an issue where the provided expiration bump is less than the current expiration, resulting in the no-op. So CLI just needs to query for the expiration in this case and provide the user with the current one. |
@vinamogit Can you try with a higher bump? |
Not sure what to put as upper limit.
This contract is the native SAC by the way. |
@vinamogit this worked for me
Very strange indeed. Tomorrow I'll have a fix that at least tell you what the current expiration is if you are under it. |
What version are you using?
What did you do?
What did you expect to see?
A successful message
What did you see instead?
error: Ledger entry not found
If you run the same command with --very-verbose yout get
The text was updated successfully, but these errors were encountered: