Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Module cache upload and run #1382

Merged
merged 2 commits into from
Apr 4, 2024

Conversation

graydon
Copy link
Contributor

@graydon graydon commented Apr 4, 2024

This covers a two cases I failed to cover in #1375 that @dmkozh and @sisuresh have identified:

  • User calls contract without putting wasm for call in footprint or storage
  • User calls upload_contract (or its equivalent, update_current_contract_wasm) mid-execution and then calls the updated-or-new contract

As well as a third case that is, as far as I know, not possible; but it seems to me it doesn't hurt to be defensive since someone could make it possible in the future fairly easily and forget to cover this case in the cache code:

  • User deletes wasm in transaction, and then tries to call it.

As always, there is probably room for a bit more testing here, but I wanted to get these cases covered and fixed asap.

This should make-redundant PR #1380

@graydon graydon requested review from sisuresh, dmkozh and a team as code owners April 4, 2024 06:22
@graydon graydon force-pushed the module-cache-upload-and-run branch from e133392 to 6722393 Compare April 4, 2024 06:25
@graydon graydon added this pull request to the merge queue Apr 4, 2024
Merged via the queue into stellar:main with commit 48f9dff Apr 4, 2024
13 checks passed
@graydon graydon deleted the module-cache-upload-and-run branch April 4, 2024 19:03
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.

2 participants