-
Notifications
You must be signed in to change notification settings - Fork 81
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
UpgradeRemote
on workspace-rs sandbox seems to behave unexpectedly
#194
Comments
UpgradeRemote
on Sandbox seems not workingUpgradeRemote
on workspace-rs sandbox seems to behave unexpectedly
Shouldn't the versions have been 2.8.0 and then 2.8.1? Why 2.7.0? |
just for checking differences, I thought middle number would be more visible. |
It seems the error happened from Access block from Aurora engine that the sender(predecessor) is not the owner of aurora contract. However, the error occurred even after I changed the owner account for the Aurora engine contract. @ctindogaru the upgrade remote callback shows that the sender is marked same as receiver_id, but it seems predecessor is marked different. This is weird as the transaction marks executor id as receiver id, but it does not act as the predecessor in the smart contract.
|
To replay this error, you can visit current aurora-dao-demo code and run |
I assume that this is not an issue of the library given my help? |
I was using
workspace-rs
to test upgrade on Aurora engine with Sputnik DAO council operation.https://github.com/hskang9/aurora-dao-demo
However, I don't see change after finalizing proposal. I thought it was because fast_forward issue, but it still did not show previous version after
UpgradeRemote
proposal finalization. Is there something that I have overlooked?logs
The text was updated successfully, but these errors were encountered: