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.
Expose memory stores to
on.stepsin pre-activation for deterministic dispatch gating #44015New 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
base: main
Are you sure you want to change the base?
Expose memory stores to
on.stepsin pre-activation for deterministic dispatch gating #44015Changes from all commits
1812bc3ee0df32ab61304315c559d6faece30c378985aabb5File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd] The write-back absence checks (
NotContains) are named after the post-agent job steps ("Commit cache-memory changes","Push repo-memory changes") — but the real silent write risk in pre-activation isactions/cache(notactions/cache/restore) auto-saving on its post-action. These two step-name checks would pass even if the wrong cache action were used.💡 Add the missing assertion
This directly tests the read-only property the PR description promises.
@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing test coverage: no case exercises the
actions/cachevsactions/cache/restoreselection in pre-activation.The test asserts that write-back steps (
Commit cache-memory changes,Push repo-memory changes) are absent frompre_activation, but it does not assert that the cache restore step usesactions/cache/restore(and not the auto-savingactions/cache). This gap means the bug described on line 243 would not be caught by this test suite.Suggested addition: add an assertion like:
(or the pinned variants returned by
getActionPin). This would concretely enforce the read-only cache contract.@copilot please address this.