Repository navigation
feat: sqb dev terminal screen, one foreground sign-in and bounded warehouse read retries - #1509
Merged
Merged
Conversation
Phase lines, tree groups, the ready card, event lines, the hotkey bar, frame rules, plain lines and in-place redraw, with snapshot tests at 80 and 120 columns and a no-wrap check at every width. Not yet wired into sqb dev.
…ehouse verdict, and takes recompile requests
# Conflicts: # crates/sqlbuild-python/src/bindings/_helpers/debug_command/run_debug.rs # tests/e2e/src/sqlbuild/cli/commands/main/debug/test_debug.py
Not wired into sqb dev yet.
…s, key reader and debug output split Key reader and connection helpers are not wired into sqb dev yet.
…ign-in, runs and keys Not yet passing fensu; plain and live modes checked by hand only.
# Conflicts: # crates/sqlbuild-python/src/bindings/_helpers/location_command/runtime.rs
…t, and the location skips a second sign-in Not yet passing fensu.
…try modules split into helpers, event emission in orchestration The Python bindings cap rises by 24 lines for the location's step events.
…s one foreground sign-in, docs state each adapter's warehouse cost
…y memory and time failures shrink the page, and sync health carries the read error
…ount in a row, dev connection tests report the foreground result, and the foreground check stops waiting once sqb debug exits
…plain sqb dev output prints the location's warnings
…dropped while sampling reconciles
…nly, so Windows prints plain lines
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.
Why
sqb devprinted a flat log with no clear phase, ready state or warehouse status. An interactive sign-in prompted inside a background step, then the sync signed in again. A failed history read halved its page and retried every 30 s forever, even when a smaller page cannot help, and the UI never showed why.Changes
sqb devscreen: start-up checklist, ready card, one line per change, publication, run or location warning, and keyso r s l q. WithNO_COLOR, CI or no terminal it prints stablesqlbuild dev:lines, warnings included.sqlbuild-core.sqb dev.sqb devwith per-adapter warehouse cost; read failures on the server page.fensu.toml: bindings crate cap 206,335 → 206,364 (step events and read-failure replies live in the runtime binding); oneFPRSL105exception for the tree-group renderer until a second screen imports it.DuckShop: not applicable; output, terminal and retry timing only, no project shape, data value or lifecycle.
Verification
test_dev.py(plain warning line on a failed read),test_dev_terminal.py(one foreground sign-in; fails on 0.232.1), warehouse metadata and catalog suites (55 pass).svelte-check; Connections checked on a realsqb devwithout its warehouse file.fensu check,make check-ci.