Siddharth Suresh

This is expected when panic is called in a wasm contract - https://github.com/stellar/rs-soroban-sdk/blob/main/soroban-sdk/src/lib.rs#L48-L53. If you want the message to propagate up, `contracterror` should be used with `panic_with_error!` documented [here](https://soroban.stellar.org/docs/examples/errors#panicking-with-an-error). @graydon...

This should be fixed before our next settings proposal. I think an easy solution would be to copy it into the example repo, and update the core command line tool...

Yeah good point. The protocol will not accept a tampered upgrade, so this isn't urgent. We need to figure something out with the current contract though because the test-wasms use...

I'm closing this because the upgrade contract is irrelevant - the protocol does not allow a tampered contract data entry for the upgrade.

@leighmcculloch Should this issue still be open? Th contract spec code has changed quite a bit so it's not clear to me what needs to be done here.

The interfaces were split in https://github.com/stellar/rs-soroban-sdk/pull/1012. We still need to provide a single interface to interact with the SAC. This can be done by exposing a trait that combines the...

So in the release workflow, a PR like https://github.com/stellar/rs-soroban-sdk/pull/1244 will catch the missing notes, and then we'd add it in that PR?

> We have this issue on a larger stage that for this image when things go wrong, it rarely stops running. Sometimes this is okay, as it would be actually...

> Looks like there are still situations where the upgrade can fail, such as if the file needs updating due to an xdr change, and the image can keep running....

I'm looking into doing something like https://serverfault.com/a/922943.