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
6 changes: 4 additions & 2 deletions quest/m0/pin-egress-dial.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

The `moq` submodule includes the two moq changes destinations dial through:
moq-rtmp's `rtmps://` dial keeps the URL-derived `tcUrl`, from
[RTMPS keeps `tcUrl`](https://github.com/moq-dev/moq/blob/main/quest/m2/rtmp-rtmps-tcurl.md),
[RTMPS keeps `tcUrl`](https://github.com/moq-dev/moq/pull/8744) (landed),
and a dial takes a policy its caller supplies, so a host can refuse private
and loopback addresses, from
[a caller-supplied dial policy](https://github.com/moq-dev/moq/blob/main/quest/m3/webrtc-dial-policy.md).
Expand All @@ -21,7 +21,9 @@ fixing whatever the new API breaks here.
## Waiting

- moq-dev/moq: both upstream quests above land. They were being planned in
moq's tree on 2026-11-09, so each link resolves once its plan merges.
moq's tree on 2026-11-09. RTMPS keeps `tcUrl` landed on 2026-11-14 as
[moq-dev/moq#8744](https://github.com/moq-dev/moq/pull/8744); the dial
policy is still open.
Check: both quests' PRs have merged on moq's `main`, deleting their files,
moq-rtmp's TLS dial sends the URL-derived `tcUrl`, and a dial takes the
caller's policy. A quest file that moved, or went away without its work
Expand Down
18 changes: 12 additions & 6 deletions quest/m0/wgpu-unpatch.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,15 +23,21 @@ egui keeps rendering through wgpu on the shared device, so the upstream fix is
the real one. wgpu's suite has no native surface, so the fork's commit carries
no test; the studio's repro is the evidence.

Decided 2026-11-19 (maintainer, /quest-complete): ✅ wait on
[gfx-rs/wgpu#10675](https://github.com/gfx-rs/wgpu/pull/10675), another
author's PR that takes `command_indices` around the HAL surface configure and
unconfigure and the queue's drop, the race the fork fixes (rejected: opening
our own PR from `surface-configure-race`). It merged on
2026-11-20 UTC. If the release that carries it still crashes the startup repro,
open the fork's remaining change upstream then.

Once a release carries it, drop the whole `[patch.crates-io]` block. If it
lands only in a new wgpu major, bump egui and eframe to the release built on
it in the same PR.

## Waiting

- Maintainer: open the gfx-rs/wgpu PR from `moq-dev/wgpu`'s
`surface-configure-race` branch, rebased onto wgpu's trunk. wgpu's
CONTRIBUTING requires the human submitter to write the PR description, so no
agent posts there. Done when the PR is open.
- gfx-rs/wgpu: merge that PR and publish a release carrying it. Check the
wgpu-core changelog on crates.io.
- gfx-rs/wgpu: publish a release carrying
[gfx-rs/wgpu#10675](https://github.com/gfx-rs/wgpu/pull/10675), merged on
trunk 2026-11-20. Check: the wgpu-core changelog on crates.io lists it in a
release.
9 changes: 3 additions & 6 deletions quest/m1/drop-winit.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,9 @@ data type, on every backend including Wayland.
- Once eframe runs on it, take drops from those events: the position from
`DragMoved`, files and `text/uri-list` or `text/x-moz-url` web addresses
from the data transfer, and delete `pointer.rs`.
- Recommended, not decided (see Waiting): no per-platform hook for web
addresses meanwhile. Each platform would need its own drag target
- Decided 2026-11-19 (maintainer, /quest-complete): ✅ dragged web
addresses wait for winit's drag API, with no per-platform hook meanwhile
(rejected: a hook per platform now). Each platform would need its own drag target
registered beside winit's (an `IDropTarget` taking `CF_UNICODETEXT`, an
`NSView` drag type for URLs, and an Xdnd type list winit owns), which the
new API makes redundant, while Ctrl+V already turns a copied address into a
Expand All @@ -36,10 +37,6 @@ data type, on every backend including Wayland.
release's `egui-winit` dependency on `winit`. A 0.30 backport of Wayland
drops ([rust-windowing/winit#4729](https://github.com/rust-windowing/winit/pull/4729))
would bring Wayland drops alone, landing at the scene's center, sooner.
- Maintainer: whether web addresses dragged from a browser wait for that
release (recommended: paste covers them, and a hook per platform is three
drag targets beside winit's to delete later) or get a hook per platform
now.

## Related

Expand Down