#stellar/quickstart:soroban-dev : version and limits?

28 messages · Page 1 of 1 (latest)

latent totem
#

Hi,
while trying to update my contracts that I test on standalone, even a 2635 bytes wasm gives me HostError: Error(Budget, ExceededLimit) during install or deploy.

I'm using this to launch quickstart:

docker pull stellar/quickstart:soroban-dev
docker run --rm -it \
    -p 8000:8000 \
    --name stellar-standalone \
    stellar/quickstart:soroban-dev \
    --standalone \
    --enable-soroban-rpc

This should reference this image: https://hub.docker.com/layers/stellar/quickstart/soroban-dev/images/sha256-99a5256d69178c785d1f21195192d34faf1cb265e467d6efc257525fb25d587c?context=explore

Any advice?

chilly dragon
#

Oof, looks like we missed merging this change to quickstart that configured the limits on standalone. We'll look at getting this merged in the next 24 hours. https://github.com/stellar/quickstart/pull/480 cc @dusk oasis

GitHub
quickstart: add soroban high limit override for standalone networks...

What ?
With the recent core build, the resource limits for soroban transactions were lowered dramatically.
On any of the public networks, there would be a process to raise these up to a reasonable ...

latent totem
#

ok, cool!

chilly dragon
chilly dragon
#

Should be fixed now. @latent totem can you rerun your contract after docker pulling the image?

latent totem
small wigeon
#

Hello, We are having the same issue:

Deploying token to network standalone
standalone
/workspace/contracts/token/target/wasm32-unknown-unknown/release/soroban_token_contract.wasm
error: transaction simulation failed: host invocation failed

Caused by:
    HostError: Error(Budget, ExceededLimit)
    DebugInfo not available

We are using te latest testing quickstart image https://hub.docker.com/layers/stellar/quickstart/testing/images/sha256-551723e0178208dd25c950bf78ab5618d47257a594654bbcaaf6cec8dc8c240c?context=explore

#

Is this latest testing image not considering the PR you mention?

#

"!

#

🤓

silent helm
#

@small wigeon if you pull the latest image (tag soroban-dev) it passes the ExceededLimit error. In my case after that error is fixed I get TxSorobanInvalid

small wigeon
#

Same for us

jolly hearth
#

I get TxSorobanInvalid
this means that tx is not accepted in the first place

#

e.g. if resources are higher than network limits. this error should get a lot more additional context, but it's not there yet

silent helm
jolly hearth
#

I can't tell what exactly is wrong without seeing the transaction. e.g. specifying 150M instructions in SorobanData will fail with this error as well, because the network limit for max tx instructions is 100M

silent helm
jolly hearth
#

it depends on what you pass in the transaction. nothing prevents you from asking for 1B instructions for a trivial operation.

#

so again, in order to make any conclusions tx envelope is required

chilly dragon
#

Looks like we accidentally left a feature turned off on the :testing image, that raised the limits to something useful.

#

The fix for this is about to be merged. CI is just running.

jolly hearth
#

that raised the limits to something useful.
that's not the live image, is it? it seems like the error occured when submitting the transaction to the network, not during preflight (as the latter simply doesn't have the said error)

chilly dragon
#

Ah ok, I misunderstood, thanks.

jolly hearth
#

it doesn't mean that preflight couldn't come up with over-the-limit estimates though...

small wigeon
small wigeon