Expose task content hash to task processes#2504
Open
gabrielbryk wants to merge 2 commits into
Open
Conversation
Merging this PR will not alter performance
|
Collaborator
|
Going to land this in 2.3 #2516 We'll see if this kind of PR is still necessary. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Expose
MOON_TASK_CONTENT_HASHto task child processes.This hash uses Moon’s task-local and toolchain hash material, but excludes upstream dependency task result hashes. Moon’s existing cache behavior remains unchanged and continues to use
MOON_TASK_HASHfor hydrate/archive/remote cache behavior.This gives external command wrappers a Moon-native static key for runtime-observed cache experiments without requiring them to reimplement Moon’s task hashing logic.
Changes
MOON_TASK_CONTENT_HASHalongsideMOON_TASK_HASH