docs: name the blocker for each uncovered live path - #29
Merged
Conversation
…econd run The v0.1 roadmap carried one unchecked box covering three unrelated gaps, which read as a single deferred task rather than three different reasons nothing can be done. Each is now named with its actual blocker: chat refuses to start without a terminal by design, chunked results are not reliably reachable because Genie bounds its own SQL, and QUERY_RESULT_EXPIRED waits on Databricks' cache schedule. Also records the second live run. The Agent-resolution change -- fetching an id directly instead of paging the listing -- alters how every ask, chat and pack run finds its Agent, and no contract test can tell you whether a real workspace agrees. All 8 live tests passed against the workspace after it.
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.
The v0.1 roadmap carried one unchecked box covering three unrelated gaps, which reads as a single deferred task rather than three different reasons nothing can be done about them.
Each now names its actual blocker:
chat— the REPL refuses to start without an interactive terminal, by design, so it cannot be driven from CI or an agent session. Its underlying follow-up call is covered live; the loop around it is not.QUERY_RESULT_EXPIRED— the cache expires on Databricks' schedule, hours later, with no way to force it.Also records a second live run: all 8 live tests passed against the real Azure Databricks workspace after the Agent-resolution change. That change alters how every
ask,chatandpack runfinds its Agent, and no contract test can tell you whether a real workspace agrees — so it was worth spending a live run on.