Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion quest/m1/ffi-refusals/moq-pin.md
Original file line number Diff line number Diff line change
Expand Up @@ -123,4 +123,10 @@ crates, which only defers the failure until a later nightly makes it a hard erro
own `Driver: Send` proof: at `rs/moq-tokio/src/client.rs:789`, on the `Instrumented<...>` from
`tokio::spawn(panic::isolate(time::run(driver)).instrument(..))`, and in the moq-ffi facade
on `moq_net::Driver: Sync`, through the lite session driver's `Publisher` and its
`kio::Tasks<Control>`.
`kio::Tasks<Control>`. Both still overflow on 2026-11-18 at moq `71c6209f` (moq-tokio's now
at `client.rs:703`); the export there fails on 16 stale excludes and 5 refusals the bump
fixes in `ffi/moq/ffi.toml`: `escape` and `unescape` on the foreign `Cow`,
`Mpegts::deserialize`'s generic `Deserializer`, and moq-tokio's `server::Streams::{tcp,
unix}` as borrowed returns that are not `Clone`. moq plans the fix in
[moq-dev/moq#9136](https://github.com/moq-dev/moq/pull/9136)'s
`quest/m1/driver-sync-depth.md`.
18 changes: 5 additions & 13 deletions quest/m2/crabx/binstall-tags.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,19 +19,11 @@ these builds.
Upstream accepted the idea on the issue, and
[cargo-bins/cargo-binstall#2752](https://github.com/cargo-bins/cargo-binstall/pull/2752)
adds both templates. Codeberg's arm reuses `GITHUB_RELEASE_PATHS`, so it gets them with no
code change; the 2026-11-14 update merged upstream's `main` and regenerated SUPPORT.md
with `just update-docs`, so both its GitHub and Codeberg lists show the templates. Its
CI on that head waits for a cargo-bins maintainer to approve the fork's run.
code change. It merged on 2026-11-15.

## Waiting

- cargo-bins/cargo-binstall: merge
[#2752](https://github.com/cargo-bins/cargo-binstall/pull/2752) and ship a release
carrying it; then bump binstalk in crabx and drop the patch. Check the PR and the
releases page.
- Maintainer: answer NobodyXu's review on #2752 (recommended reply: Codeberg's arm reuses
`GITHUB_RELEASE_PATHS`, and the regenerated SUPPORT.md lists both templates under
Codeberg), and in the same reply ask a cargo-bins maintainer to approve the fork's CI
run on the head. An agent can't take this: posting outside the maintainer's orgs needs
the maintainer, and only cargo-bins can approve the run. Check that the thread has the
reply and the head's CI has run.
- cargo-bins/cargo-binstall: ship a release carrying
[#2752](https://github.com/cargo-bins/cargo-binstall/pull/2752); then bump binstalk in
crabx and drop the patch. On 2026-11-18 the latest, v1.27.0 and binstalk v0.30.0, predate
it. Check the releases page for a newer `v*` and `binstalk-v*` release.
8 changes: 8 additions & 0 deletions quest/m3/crabx-app.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,3 +13,11 @@ hosting this project would run.

The PR adds what `crabx init` writes: [`crabx/src/binaries.yml`](/crabx/src/binaries.yml)
with the repository's default branch filled in.

Decided 2026-11-18 (maintainer, /quest-run): ✅ wait for crabx's first publish, since nothing
can install what the App sets up until then (rejected: start now; delete the App).

## Required

- [First publish](/quest/m2/crabx/first-publish.md) - crabx 0.1.0 on crates.io and npm, so
the pipeline the App opens a PR for can run
5 changes: 3 additions & 2 deletions quest/m3/session-quic.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,8 @@ Public API: the C names moq's bindings get.

## Waiting

- moq-dev/moq: the [runtime-free QUIC driver](https://github.com/moq-dev/moq/blob/main/quest/m3/quic-sansio-driver.md),
- moq-dev/moq: the [runtime-free QUIC driver](https://github.com/moq-dev/moq/blob/main/quest/m4/quic-sansio-driver.md),
planned in [moq-dev/moq#7197](https://github.com/moq-dev/moq/pull/7197), lands. moq ranks
it in m3, after its next breaking release. Done once that quest is gone from moq's `main`
it in m4, which waits on its next release cut
([moq-dev/moq#8637](https://github.com/moq-dev/moq/pull/8637) moved it from m3 on 2026-11-14). Done once that quest is gone from moq's `main`
and the driver's connections implement moq-net's `transport::poll::Session`.