Eval startup snippets explicitly #102
Merged
Conversation
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
andrus
added a commit
that referenced
this pull request
Nov 8, 2025
andrus
added a commit
that referenced
this pull request
Nov 9, 2025
removing snippets support from the builder. They are collected, but otherwise unused
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What does this PR do?
Removes implicit execution of startup snippets from CodeEvaluator.
Executes user-defined startup snippets explicitly during the kernel boot sequence.
Implicit execution could run before
JJAVA_CLASSPATHwas applied, causing failures when snippets reference classes from extra classpath.Explicit control guarantees correct ordering: default extensions -> extra classpath/extensions -> startup snippets.
Fixes #67.