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
In SDK v0.47, the --chain-id flag in queries result in an error by default. So using it returns an error.
Description
I can't find an issue to link here for why --chain-id it was removed by default, but it was removed from simapp within this refactor. To demonstrate the issue, I'll use the following test example from one of my repos:
// ...// Upload and Instantiate the contract on wasmd:codeId, err:=wasmd.StoreContract(ctx, wasmdUser.KeyName(), "../../artifacts/cw_ica_controller.wasm")
require.NoError(t, err)
store contract will always return an error in the latest version of wasmd (v0.40.2) because the StoreContract function checks whether it was successful via a query. But it will pass in an older version such as v0.32.1.
Proposal
The SDK team suggested that this flag is only passed to txs.
The text was updated successfully, but these errors were encountered:
Summary
In SDK v0.47, the
--chain-id
flag in queries result in an error by default. So using it returns an error.Description
I can't find an issue to link here for why
--chain-id
it was removed by default, but it was removed from simapp within this refactor. To demonstrate the issue, I'll use the following test example from one of my repos:store contract will always return an error in the latest version of wasmd (
v0.40.2
) because theStoreContract
function checks whether it was successful via a query. But it will pass in an older version such asv0.32.1
.Proposal
The SDK team suggested that this flag is only passed to txs.
The text was updated successfully, but these errors were encountered: