Skip to content

357 unhandeled error in sc runtime - #358

Merged
peterjah merged 2 commits into
mainfrom
357-unhandeled-error-in-sc-runtime
Sep 15, 2026
Merged

peterjah merged 2 commits into
mainfrom
357-unhandeled-error-in-sc-runtime

Conversation

@peterjah

Copy link
Copy Markdown
Contributor

No description provided.

@peterjah peterjah linked an issue Sep 15, 2026 that may be closed by this pull request
@peterjah
peterjah requested a review from bilboquet September 15, 2026 08:36

@bilboquet bilboquet left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gg !

@peterjah
peterjah added this pull request to the merge queue Sep 15, 2026
Merged via the queue into main with commit a2b2a78 Sep 15, 2026
11 checks passed
peterjah added a commit to massalabs/massa that referenced this pull request Sep 15, 2026
Picks up massalabs/massa-sc-runtime#358, which closes #4923: non-depth
failures inside a nested call are no longer reported as "Depth error",
and the wasm backtrace is no longer surfaced in error messages.

massa-proto-rs has to move in lockstep: the runtime pins 63fea52, and
leaving massa on 9bfbbe1 resolves two versions of the crate into the
same build. That bump renames operation_type::Type::ExecutSc to
ExecuteSc (prost tag unchanged) and adds PublicStatus.max_datastore_keys_query,
now populated from the existing grpc max_datastore_keys_queries setting
rather than left unset, since the node does apply that limit.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@bilboquet
bilboquet deleted the 357-unhandeled-error-in-sc-runtime branch September 22, 2026 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unhandeled error in SC runtime

2 participants