Fix non-deterministic schedule friendly format comments in compiled workflows#11373
Merged
Fix non-deterministic schedule friendly format comments in compiled workflows#11373
Conversation
Store schedule friendly formats in Compiler instance instead of global variable to prevent non-deterministic behavior across compilations Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Investigate random compilation change
Fix non-deterministic schedule friendly format comments in compiled workflows
Jan 22, 2026
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.
Schedule friendly format comments (e.g.,
# Friendly format: daily (scattered)) were appearing randomly in compiled workflows due to pointer address collisions across compilations.Root Cause
The global
scheduleFriendlyFormatsmap used frontmatter pointer addresses as keys viafmt.Sprintf("%p", frontmatter). When Go's memory allocator reused addresses, workflows retrieved formats from previous compilations:Changes
Move to per-compiler instance storage:
scheduleFriendlyFormats map[int]stringfield toCompilerstructc.scheduleFriendlyFormats = nilat compilation startAdded determinism test:
TestFriendlyFormatDeterminismvalidates no cross-compilation leakageOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.