neard-sandbox built @master from source panics at runtime

[ghost]

Describe the bug
There is a panic at runtime running neard-sandbox built from source @master. An example is when running the workspace-rs tests. The panic does not happen when using the latest nearcore release branch 1.35.0 https://github.com/near/nearcore

To Reproduce
Build neard-sandbox from source:

git clone https://github.com/near/nearcore.git
cd nearcore
make sandbox-release

Run workspase-rs tests locally:

git clone https://github.com/near/near-workspaces-rs.git
cd near-workspaces-rs
NEAR_SANDBOX_BIN_PATH="/path/to/built/neard-sandbox" NEAR_RPC_TIMEOUT_SECS=100 cargo test --verbose --features unstable

Expected behavior
Tests should run normally as in @1.35.0

Screenshots

Version (please complete the following information):

• nearcore: @master #3a56da2b76b280f7e0c42d4b4d3242b519908201
• rust version: rustc 1.73.0 (cc66ad468 2023-10-03)
• feature(s): sandbox
• system: macOS

Additional Context
I've played around with toggling sandbox and near_vm features and not found a simple fix. But I could be wrong.

[frol]

@shariffdev I can reproduce it on my side with the commit you referenced, but after that there was PR #9658 that stabilized the restriction for creation of top-level accounts, and so top-level accounts (dev-xxxxxx-xxxxx) cannot be created anymore without registrar, so this issue is masked. Please, adjust near-workspaces-rs to either (1) use the root account to create sub-accounts as dev accounts (instead of dev-xxxxx-xxxxx, create dev-xxxxx-xxxxx.sandnet or whatever we use for the root account id there); OR (2) use registrar account to continue creating dev-xxxxx-xxxxx accounts - whichever path will be faster to hack, so we can test and reproduce the issue.

[ghost]

@frol thanks for the strategies. I was able to recreate the issue still. Heres the workaround: https://github.com/shariffdev/workspaces-rs/tree/hack/tla-acc-id

[ghost]

I could not find the "registrar" account info, there was the validator_key and the node_key when initialising sandbox. Is it stored somewhere accessible?

[bowenwang1996]

@frol on the topic of top-level accounts, could workspace adjust the config in the local environment that it spins up? #9658 changes only the config value (32 -> 63).