fix(Async Queries): enable public s3 access - #605
Merged
Conversation
One instance directory serves one runtime, so the executor could not start from the recipe directory the scheduler already held the lock on. Without an executor the scheduler still marked submitted jobs RUNNING, so the recipe appeared to hang on an async query that never completed. Pass SPICE_CONFIG_DIR so the executor gets its own instance directory.
krinart
approved these changes
Aug 20, 2026
lukekim
approved these changes
Aug 21, 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
3 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.
馃棧 Description
馃敤 Related Issues
馃 Concerns