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
We noticed the dapps weren't getting wallet updates in Agoric/ui-kit#57. More details in the issue comments, but it turns out when an offer to close a vault fails (e.g. due to insufficient IST in one's purse), the vstorage update in published.wallet.agoric1[useraddress] contains an error object that cannot be parsed as valid capdata by @endo/marshal. This was causing the follower in casting to crash silently and stop yielding updates for offer statuses. This would also cause the next offer status update to fail, because when you load the dapp, it would hit this error, and the follower would crash.
To Reproduce
Steps to reproduce the behavior:
Open a vault on app.inter.trade
Try to close the vault with insufficient IST in your purse
Notice that you never see the offer status update in the toast
Expected behavior
The status update is able to be unserialized as valid capdata and the casting follower doesn't break
The text was updated successfully, but these errors were encountered:
Describe the bug
We noticed the dapps weren't getting wallet updates in Agoric/ui-kit#57. More details in the issue comments, but it turns out when an offer to close a vault fails (e.g. due to insufficient IST in one's purse), the vstorage update in
published.wallet.agoric1[useraddress]
contains an error object that cannot be parsed as valid capdata by@endo/marshal
. This was causing the follower in casting to crash silently and stop yielding updates for offer statuses. This would also cause the next offer status update to fail, because when you load the dapp, it would hit this error, and the follower would crash.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The status update is able to be unserialized as valid capdata and the casting follower doesn't break
The text was updated successfully, but these errors were encountered: