chore(execute): add missing return statement for stub contract deployment #2193
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🗒️ Description
When deploy_contract() is called with a stub parameter, it retrieves the existing contract from the chain and adds it to the allocation. However, the method was missing a return statement after handling the stub case, causing it to continue executing and attempt to deploy a new contract with the stub's bytecode.
This led to an assertion error when the retrieved bytecode (Bytes type) didn't match the expected types (Bytecode or Container) for deployment.
The fix adds a return statement after the stub handling block to properly exit the method and return the stub's contract address.
🔗 Related Issues or PRs
The related issue is the inclusion of stub contracts themseleves in #2073
✅ Checklist
tox
checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:uvx --with=tox-uv tox -e lint,typecheck,spellcheck,markdownlint
type(scope):
.mkdocs serve
locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.@ported_from
marker.