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

Handle closing of the program in the same slot as deployment #33025

Merged
merged 2 commits into from
Aug 28, 2023

Conversation

pgarg66
Copy link
Contributor

@pgarg66 pgarg66 commented Aug 28, 2023

Problem

The cache retains the deployed program even though it was closed, if the deployment and close happened in the same slot.

Summary of Changes

The tombstone for closed program was not getting inserted in the cache. This allowed the cached entry for the deployed program to remain active. This PR checks if the new entry is a tombstone, and inserts it in the cache.

Fixes #

@pgarg66 pgarg66 added the v1.16 PRs that should be backported to v1.16 label Aug 28, 2023
@pgarg66 pgarg66 marked this pull request as ready for review August 28, 2023 14:54
@pgarg66 pgarg66 requested a review from Lichtso August 28, 2023 14:54
@pgarg66 pgarg66 merged commit e036a03 into solana-labs:master Aug 28, 2023
@pgarg66 pgarg66 deleted the close-deploy-same-slot branch August 28, 2023 16:05
mergify bot pushed a commit that referenced this pull request Aug 28, 2023
mergify bot added a commit that referenced this pull request Aug 28, 2023
…backport of #33025) (#33027)

Handle closing of the program in the same slot as deployment (#33025)

(cherry picked from commit e036a03)

Co-authored-by: Pankaj Garg <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1.16 PRs that should be backported to v1.16
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants