#Seeing a lot of `txSorobanInvalid` using the local Docker quickstart

33 messages · Page 1 of 1 (latest)

halcyon coyote
#

Getting quite a lot of AAAAAAAIX57////vAAAAAA== using the local quickstart Docker.
Here's an example transaction that failed

📎 message.txt
alpine hollow
halcyon coyote
#

fwiw these same series of calls work on futurenet

#

My contract doesn't do any deploying, but it is adding to and reading from an increasingly large vector, why read_bytes and instructions grow over time

#

My understanding though was standalone had less stringent fee checks than futurenet/testnet

#

So I should be able to do more vs less in standalone

#

Sorry it's called local now

#

fwiw I'm using stellar/quickstart:testing. Lmk if there's a newer tag I should try

alpine hollow
#

I suspect stellar-core's high override feature is buggy.

#

I'd like to get quickstart off of using that flag, and get it updated to use the stellar-core config, but the config is currently updated via a gnarly python script, and there's this stellar-core issue to clean that up:

#

@polar vector Is there a plan to prioritize ☝🏻 ?

polar vector
alpine hollow
#

We've actually got a fix building at the moment.

halcyon coyote
#

Can confirm this update fixed my issues. I HAVE SO MUCH POWER NOW!!!

#

Testing on local is so nice, lighter limits, faster speeds, SWEET

alpine hollow
#

If the limits were available on an endpoint of the rpc, the cli could output how close you are to limits.

halcyon coyote
#

I may try and rough something up soon since the simulation gives you a lot of stuff, I'm just not sure it gives you all the stuff

#

RAM in particular I'm finding is a tough one as it's never surfaced back This isn't true it's surfaced back in the response to the sim just outside the sorobanData

#
  • Events & return value size I think I could get this back from the sim I'd just need to be sure I was including the right values to derive the correct sum
  • Ledger entry size I'm not quite sure what that is but I'd imagine it's somewhere in there. The rest I believe I already know how to get
halcyon coyote
#

I give to you sorobill. Pass it a simulation json file and it will output a response of the fees. If you use the local Docker quickstart you can gen simulations far above those of the Phase 1 futurenet and testnet which can help with finding where you may be exceeding limits.

e.g. ./sorobill --file ./simulation_response.json

{
  CPU_instructions: 18752917,
  RAM: 2629481,
  ledger_entry_reads: 2,
  ledger_entry_writes: 12,
  ledger_write_bytes: 4112,
  ledger_read_bytes: 32428,
  events_and_return_value_size: 2236
}
📎 sorobill
#

You can see from this in my case events_and_return_value_size > 2 KB or 2,024 bytes which would break in futurenet / testnet according to the current Phase 1 limits

dusty elbow
#

@half grail @wispy temple tyler's tool auto calculates the usage... wanna give it a go for our chat re: limits.

delicate hemlock
halcyon coyote