Repository navigation
Merged
Conversation
…ty, and show weft's own calls that keep failing - Body-less POSTs (a run handed to a worker, a role's tick, the CLI's empty POSTs, a token exchange) send Content-Length: 0. Google's front end refused them with 411 over HTTP/1.1, which left every cloud install unable to start infra or run anything. They stay HTTP/1.1: HTTP/2 would put a worker's held run calls on one connection capped at 100. - A route on the install's shared address sits under its project: /connect/<tenant>/<project id>/<path>. Two projects may serve the same path; the overlap check compares one project's triggers. Stored routes are rewritten by a data migration. - weft's calls that keep failing (a role it cannot wake, workers it cannot hand a run to) are kept in unanswered_call and shown by weft status, weft infra status and the infra wait line. - Activate while infra is changing names the infra as the blocker. - Terraform makes Cloud Logging's service agent before the sink that writes as it. - The assistant setups say to run independent work on parallel agents. - Docs, Tangle skills and the connect library speak the new address; both extensions bumped.
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.
Fixes from the latest Tangle deploy round.
Content-Length, which Google's front end refuses. They now sendContent-Length: 0(weft_core::net::EmptyBody). HTTP/2 was tried and rejected: it multiplexes a worker's held run calls on one connection, which Cloud Run caps at 100 streams./connect/<tenant>/<project id>/<path>(weft_core::route::SharedMount); the overlap check is per project. A data migration rewrites stored routes. A project's own port and API domain are unchanged.unanswered_calltable and shown byweft status,weft infra statusand the infra wait line.Checked locally: workspace nextest, doc tests, clippy, parse-only build, examples, all db tests, JS checks, docs build, and the e2e tests covering same-path projects, live routes, a project's own address and the infra-change refusal.