Repository navigation
Show dropped fires, bound CLI requests, start runs through a task, check a resync before take-down - #116
Merged
Conversation
…nd check a resync before it takes triggers down - A fire or live call refused before any run starts is counted per trigger with its last reason (door_count.reason), by the worker's door and by the dispatcher, and shown in weft status and the editor. - Every CLI request has a time limit (2 minutes, or a long poll's hold and 30s); one that runs out is looked at again where the caller loops. Requests the install answers only when its own work is done keep none. - weft run hands the start to a start_run task under an id the CLI makes, follows it, and says what it is doing; the run is named after the task, and a program's run start after its call, so a start asked again answers the run it started. - A resync asks the listener whether each trigger it brings back could come up on this install (a provider subscription needing an internet-reachable address) and refuses before taking anything down. - weft resync says where it is every 30 seconds; a stale bake says what moved; an unreadable bake row no longer hides the others; the schema pass names the lock it gave up on; --json failures are documented for scripts and the CI template checks them.
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.
What a real update to 0.2.282 showed, made either impossible or loud with the way out named.
What breaks
weft runstarts the run through astart_runtask: the install answers the start at once (a task id the CLI makes, which the run is named after) and the CLI follows it, saying every half minute what the start is doing. A CLI and an install on either side of this change cannot start runs together.--jsonmust check the exit code (documented; theweft ci addtemplate does).What is new
door_count.reason, migrationworker_door_dropped_fire_reasons), by the worker's door and by the dispatcher, and shown inweft statusand the editor (dropping).POST /check, kinds decide; provider events ask the broker's new/v1/access/subscription/check) whether each trigger it brings back could come up on this install, and refuses before taking anything down. It also says where it is every 30s.Checked locally before the push: full nextest, doc tests, clippy -D warnings, parse-only compiler, examples, hakari, terraform validate and moved targets, every database suite, every JS package, the bridge, postgres credential and tangle tests, the browser extension, the docs build; e2e
seed_moved_file,lifecycle_transitions::deactivate_and_resync_wait_for_or_cancel_the_running_run,maintenance::a_trigger_comes_back_after_the_maintenance,working_copies::a_program_writes_another_projects_code_and_runs_it.