cmux-app-ffi links the host budget C ABI; dispatch pressure flags read worst first (step A of the host pressure FFI move) by lawrencecchen · Pull Request #31937 · manaflow-ai/cmux

lawrencecchen · 2026-11-02T06:50:20Z

Step A of the two-step FFI move of the app's host pressure copy (backlog A10). The host CPU/RAM budget crate from #31799 (cmux-host-budget, which acpmux's daemon already uses) is linked into cmux-app-ffi, so the next CCmuxAppFFI release carries its C ABI. No Swift change and no behavior change: nothing in the app calls the new symbols until step B.

Check the app FFI pin: expected, step A of a two-step FFI move.

Takes back #28790: #28790 reverted one entry of headers_in in scripts/cmux-next/build-app-ffi.sh (the chat index mirror header, which had landed without its release and pin). This PR does not add that entry back: it adds a different header, cmux-host-budget/include/cmux_host_budget_ffi.h, as the next entry of the same list, and lands it by the two-step FFI order (step A here, then the bot's release and re-pin, then step B), which is the order #28790 asked for.

What changes

cmux-app-ffi depends on cmux-host-budget with default-features = false (no tokio; its Cargo.lock gains no tokio) and re-exports its C ABI as host_budget, as it does the palette ranker.
scripts/cmux-next/build-app-ffi.sh ships cmux-tui/crates/cmux-host-budget/include/cmux_host_budget_ffi.h as the module CCmuxHostBudgetFFI; its cmux_* functions join the export list.
.github/workflows/app-ffi-release.yml: cmux-tui/crates/cmux-host-budget/** joins the push paths. The crate is now an FFI input (check-app-ffi-pin.sh --list-inputs lists it), and without the path a change to it would publish no release. scripts/cmux-next/tests/app-ffi-release-paths.test.sh passes. This is the only workflow change; no step, job or trigger changes.
The fix the cmux-host-budget: the host CPU/RAM budget in one Rust crate, with the app's level rules and their C ABI (no FFI input yet) #31799 review asked for before any caller: cmux_host_budget_with_pressure_json now takes the dispatch source's DISPATCH_MEMORYPRESSURE_* flags as they come and reads them worst first (4 critical, then 2 warn, then 1 normal, else unknown), as the Swift monitor (HostPressureMonitor.swift) does. One difference from Swift stays: an event with none of the three flags reads unknown here and .normal in Swift. That case cannot happen, because the source's event mask is [.normal, .warning, .critical]; step B lists it with the other differences. Before, it read one exact level, so a combined event of 6 read "unknown" and dropped the memory reason. The sysctl mapping in evaluate (pressure_word) is unchanged, so acpmux's verdicts are the same.
No dirs in the crate: dirs brings option-ext (MPL-2.0) into the app library, and the app crate license gate does not allow MPL-2.0. src/home.rs keeps the rule of dirs::home_dir (dirs-sys 0.5): first $HOME when it is set and not empty; else the passwd entry of the real user (getuid, getpwuid_r, a buffer of _SC_GETPW_R_SIZE_MAX bytes or 512, no retry); else none. Android, iOS and Emscripten read no passwd entry. home_tests.rs tests a set HOME, an unset HOME and an empty HOME. cmux-app-ffi/Cargo.lock loses dirs, dirs-sys, option-ext and the crates they brought in.
scripts/cmux-next/check_app_crate_licenses.py names cmux-host-budget as a first-party GPL crate of the app closure, so the real gate does not report it. The gate also reports cmux-motion. That is a base finding, and the follow-up PR fixes it.
The async meter tests are behind the tokio feature, so the crate's tests also build without default features (the configuration cmux-app-ffi links).

Step B, after the re-pin is on feat: CmuxNextHostPressure calls this ABI and its Swift formula, sampler, verdict init, with(pressure:) and tracker are deleted; Swift keeps the dispatch source, the 15 s timer, the daemon read, the last verdict and the views. Step B lists the verdict differences between the Swift copy and the daemon's code.

Risk: high (touches app-ffi-release.yml). Lands on an independent Review (<reviewer>): SHIP at <head> receipt.

Changelog

none

Observed / Not run

Observed at the head 515c0b9. This is my plain merge of feat-cmux-next. It brings in #31927 (the hover C ABI in cmux-app-ffi) and #32374 (the host pressure warning is off by default, with a palette toggle). The only conflict was the module doc in cmux-app-ffi/src/lib.rs, and I kept both sides. The Swift files are the same as on feat:

Panic ratchet 34d49d140856819bc09dfb75 and clippy 47247376426894db2734ca75: PENDING.

At 12232b6 these passed: panic ceedc091d22484e704d9e818 and clippy 50ecb9b70b3061cb96ea16c4. The PR comment issuecomment-6581650029 classifies the two red checks at that head: "Check the app FFI pin" is the expected step A red, and the daemon test is a load timeout in SnapshotSessionBarrierTests.

Observed at the head 12232b6. This is my plain merge of feat-cmux-next. It brings in #32282, the fix for the read_paths.rs clippy base red, and cmux-cloud-start-core, which joins the app FFI:

Panic ratchet ceedc091d22484e704d9e818 and clippy 50ecb9b70b3061cb96ea16c4: PENDING.
Lockfiles: the cmux-tui/crates/cmux-app-ffi PR check at this head and the fleet clippy, both with --locked.

At bf3bd79 (cmux-bot's merge; an independent SHIP was given there), clippy 6ca0c072d77b9feff4d3504a was red only on the base red in cmux-tui-core/src/mux/tests/read_paths.rs (lines 201, 244, 249 and 237). #32177 added it, and #32282 fixes it. The PR comment classifies it.

Observed at 3aa5af9 (the PR's own last commit; an independent SHIP was given there):

test home::tests: passed on Linux (1e06ba3c0988e5a9ae3f5385) and on macOS (109cb7f6af94f5b91f2f255a).
Panic ratchet: head 31b7cb94e3a9cf591fae2af3, base 7ea60b1 cbda8d3d961010a620fcec9a. Both show the same counts, cmux-tui indexing_slicing 835 > 831 and string_slice 84 > 82. That is the base red from NEXT Cloud DEV integration: new Worker and app-server link #28950. The PR has 0 own hits.
clippy b2bb2529555cafb701f3bbce: red only on cmux-tui-core output_store/snapshot.rs:537 too_many_arguments. That is a base red that fix(cmux-tui-core): snapshot_written takes the snapshot's end as one value (base red: clippy too_many_arguments) #32092 fixes. The PR has 0 own hits.

Observed earlier (fleet, Linux), for the change that has not changed since:

Red at 987967a (the new flag tests, still on the old exact-level mapping), test json::tests, job fc6ead8a4bb87f71e43b134f: the two new tests fail (the_dispatch_flags_read_worst_first, a_combined_critical_event_keeps_the_memory_reason). The other 7 pass.
Green at 9e29d1c (the PR's own last commit; bda755a only merges feat into it): the whole cmux-tui workspace test, job b55e0534d1695a1e226a711a. All cmux-host-budget and cmux-app-ffi tests pass. 8 tests fail, and each also failed when the rerun ran it alone. None of them is in a file that this PR changes:
- 3 terminal_host_recovery::host_death::kill_all_restore tests: a Linux base red from fix(cmux-tui): a kill of everything restores each terminal's exact text, then the session line, in the same directory string (REOPEN-F3) #31643, which the REOPEN-F3 owner has.
- cmux-tui-core connection_handler_owns_every_router_connection_operation: a base red from feat(chief): continue stopped turns and retry replies in Home #30774. base red: the router owns 58 connection operations (chief.continue, chief.retry from #30774) #31939 fixes it.
- 4 that also fail alone at the base 64b2566:
  - acpmux every_test_binary_runs_in_the_hermetic_environment (5472a06e7265dc6ae1ebaa3d; from acpmux: a stopping daemon's retry pass yields and is bounded; only the lock holder unlinks the socket; a lost socket is bound again #31593)
  - cmux-tui share_chat_waits_for_the_owners_answer (b973957eb8a382f63c3d57c0; from cmux NEXT: a guest link an agent or script asks for waits for the owner's Allow (#30263) #30550)
  - cmux-tui agent_message_launch_credential (fae49a161128474d850f2ae9) and agent_message_reply_in_place (e67e80ddb524176ae2196fba): both are a tokio worker stack overflow (SIGABRT) at the base too.
Panic ratchet at 9e29d1c, job 4933a9b07161ec03e933c9f3, and at the head bda755a, job 55fb7ac3fa1b825aeb6f500f: both passed. This PR adds no unwrap, expect, panic or indexing in production code.
fmt at 9e29d1c, job 4c44dee9b4a6c1cafe72e284: passed.
clippy at the head bda755a, job dffc83f5f08aa4b8f58d36d8: passed. At 9e29d1c (5a9189ff5de8a62034f38b8e), clippy was red only on the base red in cmux-tui-core agent_chat_notices.rs; base red: agent_chat_notices clippy (obfuscated if/else, a missing ;, a redundant clone) from #31770 #31907 fixed it, and the bot's merge brought that fix in.
Lockfiles: both were written on an agent VM with cargo metadata --offline. The proof that they resolve is in jobs that ran cargo with --locked at the head bf3bd79:
- cmux-app-ffi/Cargo.lock: the PR check cmux-tui/crates/cmux-app-ffi (workflow "rust workspaces", run 41442794928). It ran cargo clippy --locked --workspace --all-targets -- -D warnings and cargo test --locked --workspace in cmux-app-ffi, and passed.
- cmux-tui/Cargo.lock: the fleet clippy 6ca0c072d77b9feff4d3504a, which runs cargo clippy --workspace --locked.
swift-logic-lines.py: swift_logic_lines is 415771 at the head 9e29d1c and 415771 at the base 49aee50; mirror_lines is 70597 at both. There is no Swift change. Step B lowers them.

Review: independent SHIP at bda755a (the bot's merge of feat a7f48bb). cmux-bot merged feat again at 09:56Z (head 5937437, feat 7ea60b1); neither merge changes this PR's files, and the head gets its own review receipt. Its non-blocking notes go to step B so that this head stays the reviewed one: the pressure_word doc still names the dispatch flags, and with --no-default-features meter_tests.rs imports incident but does not use it (a warning, not an error).

The configuration the app links (cmux-host-budget without default features, inside cmux-app-ffi):

The PR check cmux-tui/crates/cmux-app-ffi (workflow "rust workspaces", run 41416238787, at bda755a, Linux) ran cargo clippy --locked --workspace --all-targets -- -D warnings and cargo test --locked --workspace in cmux-app-ffi. It compiled cmux-host-budget with default features off, and both passed.
macOS compile and the C ABI tests of the crate: test ffi::tests --os macos, job 3a62fddc76e968d8a2aa2ca3 on aws-m4pro-3: passed.

Not run:

The release recipe itself (scripts/cmux-next/build-app-ffi.sh: the release slices, the prelink with the export list, xcodebuild -create-xcframework). The fleet refuses it: the script is not on the controller's ci-step allowlist ("invalid ci-step: script is not on the ci-step allowlist"). app-ffi-release.yml runs it after landing. Anything in Swift.

The review of #31799 found that cmux_host_budget_with_pressure_json reads its argument as one level (1, 2 or 4) and anything else as unknown. The app's dispatch source gives bit flags, and the Swift monitor reads them worst first: an event of 6 (warn and critical) is critical. Passed raw, a critical event would read unknown and drop the memory reason. These tests ask for the Swift reading (6 and 7 critical, 3 warn, 0 and 8 unknown) through the JSON call and the C ABI. Red step: they fail on the current exact-level mapping. The async meter tests now build only with the `tokio` feature, so the crate's tests also run with --no-default-features (the configuration cmux-app-ffi links).

Step A of the two-step FFI move of the app's host pressure copy (CmuxNextHostPressure). No Swift change: the app keeps its Swift copy until the re-pin lands and step B calls this ABI. - cmux-app-ffi depends on cmux-host-budget without its `tokio` feature and re-exports its C ABI as `host_budget` (as it does the palette ranker); its Cargo.lock gains no tokio. - build-app-ffi.sh ships include/cmux_host_budget_ffi.h as the module CCmuxHostBudgetFFI. - app-ffi-release.yml publishes on a change to the crate, which is now an FFI input (check-app-ffi-pin.sh --list-inputs lists it; app-ffi-release-paths.test.sh: ok). - cmux_host_budget_with_pressure_json takes the dispatch source's flags as they come and reads them worst first (4, then 2, then 1, else unknown), as the Swift monitor does: 6 is critical, 3 is warn. The sysctl level keeps its exact mapping (pressure_word), so acpmux's verdicts do not change.

github-actions · 2026-11-02T06:50:35Z

cmux status _{(one comment, edited in place; each line is updated by the job that owns it)}

Review 515c0b9: HQ feed card · gallery before/after runs · checks

App of this head (app.zip, kept 1 day)

gh workflow run reload-build.yml -R manaflow-ai/cmux --ref feat-cmux-next -f tag=pr31937 -f ref=rust-migration/host-pressure-ffi-a -f platform=macos -f backend_mode=local

red: cmux-next checks (god files, concurrency, crash safety, l10n); no finished base run on 8390f22 to compare; do not merge until green; see lane-rules

blacksmith-sh · 2026-11-02T06:58:51Z

Found 6 test failures on Blacksmith runners:

Failures

Test	View Logs
`/tmp/tmp3qkr3b6_/summary-missing.json (live):/summary-missing.json (live):`	View Logs
`/tmp/tmpeltkl67p/summary-fail.json (live):/summary-fail.json (live):`	View Logs
`[new_workspaces] debug.new_workspace timed 0 of 50 new workspace rows/` `[new_workspaces] debug.new_workspace timed 0 of 50 new workspace rows`	View Logs
`[new_workspaces] the window draws no frames/[new_workspaces] the window draws no frames`	View Logs
`[tabs] debug.tab_switch timed 0 of 40 switches/` `[tabs] debug.tab_switch timed 0 of 40 switches`	View Logs
`[tabs] the window draws no frames/[tabs] the window draws no frames`	View Logs

^{Need help on this PR? Tag @codesmith-bot with what you need.}

teamleaderleo · 2026-11-02T08:44:25Z

Review (codex gpt-6.1-sol xhigh, next-review): SHIP at 9e29d1c

SHIP at 9e29d1c
Visual verdict: no images; Leo tries the build

No correctness findings. Release-path test, shell checks, and C-header syntax check passed; Rust tests and the macOS xcframework build could not run here.

Follow-ups: none

teamleaderleo · 2026-11-02T09:26:50Z

Review (codex gpt-6-astra high, next-review): SHIP at bda755a

SHIP at bda755a

Visual verdict: unchanged by this diff

Reviewed the FFI, feature gating, lockfile, export packaging, pressure flag mapping, and release paths. app-ffi-release-paths.test.sh passes; Rust tests were unavailable because Cargo is not installed.

Follow-ups: none

lawrencecchen · 2026-11-02T09:28:02Z

Review (claude-review-subagent): SHIP at bda755a

Checked: the merge leaves the PR paths unchanged; dispatch_pressure_word reads 4, then 2, then 1, like HostPressureMonitor.swift:133 (one difference: an event with no known bit is unknown here and normal in Swift, which cannot happen with that event mask); pressure_word and evaluate are unchanged; both new json tests and the ffi loop fail on the old exact-level mapping. Nothing outside cfg(feature = "tokio") needs tokio; the 10 header functions match ffi.rs and are the only names the export grep picks up, with no collision with the other four headers; the cmux-app-ffi Cargo.lock adds cmux-host-budget, dirs, tracing and their dependencies, and no tokio.
Workflow: one push path is added, with no trigger, permission, step or secret change; app-ffi-release-paths.test.sh is ok; rustfmt --check is clean. The red 'Check the app FFI pin' is this step A's expected red (as with #31925, then #31974) until the re-pin lands. I did not compile or run any tests.

lawrencecchen · 2026-11-02T10:08:26Z

Review (subagent, correctness first): SHIP at 5937437

Checked: the merges bda755a and 5937437 leave the PR's files the same as 9e29d1c (the diff is empty), and the diff from the merge-base 7ea60b1 contains only the 15 PR files. feat a7f48bb..7ea60b1 changes nothing in cmux-host-budget, cmux-app-ffi, build-app-ffi.sh, app-ffi-release.yml or acpmux host_pressure. The newer feat tip f22cb91 (#31945) merges cleanly with git merge-tree. app-ffi-release-paths.test.sh passes and rustfmt --check passes. #28790's chat-mirror entry does not come back, so the Takes back line is true.
The change is correct: the flags are read worst first (4, then 2, then 1, else unknown), the same as HostPressureMonitor.swift, and pressure_word for the sysctl does not change. The 10 header functions equal the 10 no_mangle exports and do not collide with the other headers. The lock has no tokio.
Non-blocking, for step B: check_app_crate_licenses.py FIRST_PARTY_GPL does not list cmux-host-budget (cmux-motion is missing too), and dirs brings option-ext (MPL-2.0) into the app FFI closure. CI runs only the unit tests of that gate, so no check is red; a manual run of the gate would flag both.

lawrencecchen · 2026-11-02T16:04:35Z

Classification, added at 515c0b9: clippy 47247376426894db2734ca75 failed only on cmux-tui/crates/cmux-tui-core/src/server/capabilities.rs:324 (unused_qualifications). This is a base red from #32380, in a file this PR does not touch. The SWITCH FRAMES owner is fixing it. The crates of this PR (cmux-host-budget, cmux-app-ffi) are clean in this run.

teamleaderleo · 2026-11-02T18:02:20Z

Review (codex gpt-6-astra high, next-review): SHIP at d7b04a5

SHIP at d7b04a5

Visual verdict: no images; Leo tries the build

[P2][follow-up] ffi.rs: cmux_host_budget_with_pressure_json changed from a level to bitmask semantics, but the ABI version remains 1. Bump the version so consumers can detect this contract change.
[P2][follow-up] app-ffi-release.yml: the release smoke link and cross-build header parity check omit the new CCmuxHostBudgetFFI header and symbols, so packaging errors in this ABI can pass CI until Swift uses them.

Follow-ups:

[P2][follow-up] Bump the host-budget ABI version for the changed pressure argument semantics.
[P2][follow-up] Add CCmuxHostBudgetFFI to the release smoke and parity checks.

teamleaderleo · 2026-11-02T20:34:29Z

Review (codex gpt-6-astra high, next-review): SHIP at 74798fc

SHIP at 74798fc
Visual verdict: no images; Leo tries the build

Focused release-path and license tests pass; supplied CI covers compilation and tests. No correctness findings.

Follow-ups: none

teamleaderleo · 2026-11-02T22:15:35Z

Review (codex gpt-6.1-sol xhigh, next-review): SHIP at ec1ad74

SHIP at ec1ad74

Visual verdict: no images; Leo tries the build

Focused workflow, license, release-path, and C-header checks passed. No correctness findings.

Follow-ups:

[P2] [follow-up] No after-image artifact was available for this head, so visual comparison remains unverified.

lawrencecchen added 2 commits November 2, 2026 06:42

lawrencecchen added the risk:high Risk tier (docs/ci/risk-tiers.md) label Nov 2, 2026

lawrencecchen temporarily deployed to artifacts November 2, 2026 06:55 — with GitHub Actions Inactive

lawrencecchen temporarily deployed to sentry-dsyms November 2, 2026 06:55 — with GitHub Actions Inactive

lawrencecchen temporarily deployed to artifacts November 2, 2026 06:57 — with GitHub Actions Inactive

teamleaderleo removed the risk:high Risk tier (docs/ci/risk-tiers.md) label Nov 2, 2026

github-actions Bot added the risk:high Risk tier (docs/ci/risk-tiers.md) label Nov 2, 2026

Merge branch 'feat-cmux-next' into rust-migration/host-pressure-ffi-a

bda755a

cmux-bot Bot temporarily deployed to ci-routing-agent November 2, 2026 08:52 Inactive

cmux-bot Bot temporarily deployed to sentry-dsyms November 2, 2026 09:02 Inactive

cmux-bot Bot temporarily deployed to artifacts November 2, 2026 09:02 Inactive

cmux-bot Bot temporarily deployed to artifacts November 2, 2026 09:04 Inactive

github-actions Bot temporarily deployed to ci-routing-agent November 2, 2026 09:06 Inactive

teamleaderleo removed the risk:high Risk tier (docs/ci/risk-tiers.md) label Nov 2, 2026

github-actions Bot added the risk:high Risk tier (docs/ci/risk-tiers.md) label Nov 2, 2026

lawrencecchen added ready-to-land Reviewed at this head; next-autoland merges it into feat-cmux-next when its only reds are base reds and removed ready-to-land Reviewed at this head; next-autoland merges it into feat-cmux-next when its only reds are base reds labels Nov 2, 2026

Merge branch 'feat-cmux-next' into rust-migration/host-pressure-ffi-a

5937437

cmux-bot Bot temporarily deployed to ci-routing-agent November 2, 2026 09:56 Inactive

lawrencecchen removed the ready-to-land Reviewed at this head; next-autoland merges it into feat-cmux-next when its only reds are base reds label Nov 2, 2026

cmux-bot Bot temporarily deployed to sentry-dsyms November 2, 2026 10:06 Inactive

cmux-bot Bot temporarily deployed to artifacts November 2, 2026 10:06 Inactive

lawrencecchen temporarily deployed to artifacts November 2, 2026 16:03 — with GitHub Actions Inactive

lawrencecchen mentioned this pull request Nov 2, 2026

cmux-tui: base red: clippy unnecessary qualification in capabilities.rs (from #32380) #32442

Merged

lawrencecchen temporarily deployed to artifacts November 2, 2026 16:06 — with GitHub Actions Inactive

github-actions Bot temporarily deployed to ci-routing-agent November 2, 2026 16:07 Inactive

cmux-bot Bot added stack-blocker and removed stack-blocker labels Nov 2, 2026

Merge branch 'feat-cmux-next' into rust-migration/host-pressure-ffi-a

d7b04a5

cmux-bot Bot temporarily deployed to ci-routing-agent November 2, 2026 17:32 Inactive

cmux-bot Bot temporarily deployed to artifacts November 2, 2026 17:44 Inactive

cmux-bot Bot temporarily deployed to sentry-dsyms November 2, 2026 17:44 Inactive

cmux-bot Bot temporarily deployed to artifacts November 2, 2026 17:48 Inactive

github-actions Bot temporarily deployed to ci-routing-agent November 2, 2026 17:49 Inactive

teamleaderleo removed the risk:high Risk tier (docs/ci/risk-tiers.md) label Nov 2, 2026

github-actions Bot added the risk:high Risk tier (docs/ci/risk-tiers.md) label Nov 2, 2026

cmux-bot Bot added stack-blocker and removed stack-blocker labels Nov 2, 2026

Merge branch 'feat-cmux-next' into rust-migration/host-pressure-ffi-a

74798fc

cmux-bot Bot temporarily deployed to ci-routing-agent November 2, 2026 19:42 Inactive

cmux-bot Bot temporarily deployed to sentry-dsyms November 2, 2026 19:53 Inactive

cmux-bot Bot temporarily deployed to artifacts November 2, 2026 19:53 Inactive

cmux-bot Bot temporarily deployed to artifacts November 2, 2026 19:57 Inactive

github-actions Bot temporarily deployed to ci-routing-agent November 2, 2026 19:58 Inactive

teamleaderleo removed the risk:high Risk tier (docs/ci/risk-tiers.md) label Nov 2, 2026

github-actions Bot added the risk:high Risk tier (docs/ci/risk-tiers.md) label Nov 2, 2026

Merge branch 'feat-cmux-next' into rust-migration/host-pressure-ffi-a

ec1ad74

cmux-bot Bot temporarily deployed to ci-routing-agent November 2, 2026 21:42 Inactive

Navigation Menu

Repository navigation

cmux-app-ffi links the host budget C ABI; dispatch pressure flags read worst first (step A of the host pressure FFI move) - #31937

cmux-app-ffi links the host budget C ABI; dispatch pressure flags read worst first (step A of the host pressure FFI move)#31937
lawrencecchen wants to merge 13 commits into
feat-cmux-nextfrom
rust-migration/host-pressure-ffi-a

lawrencecchen commented Nov 2, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Nov 2, 2026 •

edited

Loading

Uh oh!

blacksmith-sh Bot commented Nov 2, 2026 •

edited

Loading

Uh oh!

teamleaderleo commented Nov 2, 2026

Uh oh!

teamleaderleo commented Nov 2, 2026

Uh oh!

lawrencecchen commented Nov 2, 2026

Uh oh!

lawrencecchen commented Nov 2, 2026

Uh oh!

lawrencecchen commented Nov 2, 2026

Uh oh!

teamleaderleo commented Nov 2, 2026

Uh oh!

teamleaderleo commented Nov 2, 2026

Uh oh!

teamleaderleo commented Nov 2, 2026

Uh oh!

This branch was previously deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

lawrencecchen commented Nov 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What changes

Changelog

Observed / Not run

Uh oh!

github-actions Bot commented Nov 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

blacksmith-sh Bot commented Nov 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Failures

Uh oh!

teamleaderleo commented Nov 2, 2026

Uh oh!

teamleaderleo commented Nov 2, 2026

Uh oh!

lawrencecchen commented Nov 2, 2026

Uh oh!

lawrencecchen commented Nov 2, 2026

Uh oh!

lawrencecchen commented Nov 2, 2026

Uh oh!

teamleaderleo commented Nov 2, 2026

Uh oh!

teamleaderleo commented Nov 2, 2026

Uh oh!

teamleaderleo commented Nov 2, 2026

Uh oh!

This branch was previously deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

lawrencecchen commented Nov 2, 2026 •

edited

Loading

github-actions Bot commented Nov 2, 2026 •

edited

Loading

blacksmith-sh Bot commented Nov 2, 2026 •

edited

Loading