Repository navigation
Refresh OpenShell CI token during long evals - #104
Draft
tarun-etikala wants to merge 2 commits into
Draft
tarun-etikala wants to merge 2 commits into
tarun-etikala wants to merge 2 commits into
Conversation
This branch has not been deployed
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
1 participant
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.
Long Forge evaluations can outlive the roughly five-minute OpenShell OIDC client-credentials token. The first sandbox starts, but later artifact downloads and the next case fail with
ExpiredSignaturebecause the CLI has no refresh token.Refresh the CLI token cache every two minutes for the lifetime of the evaluate step. Each replacement is atomic, and the temporary response and cache stay private. This leaves the agent and scoring configuration unchanged.
Validation: YAML and shell syntax checks, plus 16 focused pipeline tests passed. In a clean-source run with Harness #9 and Flow #101, both cases completed after the refresh with no
ExpiredSignature; the older image still failed the separatepublished_briefgate. With the fixture/image change in Flow #103, two clean-source runs succeeded all five Tasks and passed publication: run 1, run 2. The second run's first case lasted about 13 minutes and the next sandbox still started successfully.Companion changes: Harness #9 and Flow #101/#103.