Repository navigation
Merged
Conversation
… own copies, have the install register a built version itself, and let an idle worker go quiet - Skipping a question ends the waiting step skipped (outputs closed, normal propagation); frozen examples record how every wait ended; a skip on a trigger is refused. - StopTagged queues its stop with the plain enqueue again. - StartInfra, StopInfra, TerminateInfra, ActivateTriggers and DeactivateTriggers take an optional instance; inputs can be requiredWhenWired. - Google connections always ask who the account is, so a Gmail-only connection works; GmailSend gains a `from` input. - A build answers at once; the install registers the version itself when its image builds end, in ask order per project; the CLI follows it and tells an unreachable cloud install apart. - An idle worker stops ticking the broker and wakes on work without making a run wait; a metered answer silent for a minute, or on a cancelled run, is cut and its cost booked. - The editor names the triggers that are off; CHANGELOG and the releasing skill keep the changelog per release.
- An answer or a cancel for a running run is written with a news entry in the same transaction; a separate teller publishes it on the install's news bus (Pub/Sub on GCP, nothing locally, where the database's own signal covers it) and retries until it goes out. - Broker processes hear the news and pass it to the worker down the line it already holds, answers the same way as cancels; the held answers request and its periodic re-reads are gone. - While every run on a worker only waits, the worker stops ticking and vouches for its runs until the first wait would give up; the reaper sleeps until the earliest lease could lapse. - A worker whose runs all only wait stops itself before the broker's request limit cuts its line, handing back what can pause and ending what cannot with the limit named; a busy worker reconnects as before. - The dispatcher and the broker no longer hold their database listening busy while a request is held, so a quiet watch lets the database sleep. - CHANGELOG names this release.
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.
Two rounds of work, both reviewed and tested before this PR.
What a person updating will notice (see
CHANGELOG.md,2026-10-11 (0.2.267)):instance; inputs can berequiredWhenWired.weft resyncorweft build).Checked locally before pushing: everything
ci.ymlanddocs.ymlrun (nextest, doc tests, clippy, the parse-only build, examples, Terraform validate, every db suite, the JS packages and extensions, the WhatsApp bridge tests, the docs book), plus the end-to-end tests covering questions, skips, cancels, parked routes, job waits, builds and route limits. The Pub/Sub path and the self-stop are covered by tests against stand-ins only; a cloud round confirms them for real.