Repository navigation
ci: queue and link from the kixel-ai org - #740
Merged
Merged
Conversation
rust2 moved from moq-dev to kixel-ai. The queue build's reusable workflow ref, the crates' repository metadata, the driver's bug report URL, and every doc and quest link now name kixel-ai/rust2. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kixelated
enabled auto-merge
November 13, 2026 04:25
Collaborator
Author
|
@pullfrog review this pull request. Its base requires an approving review, and Pullfrog's installation did not cover rust2 when this PR was opened after the move to kixel-ai. (Written by Claude Opus 5.5) |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
The whole PR: the repository rename's CI and metadata edits, the mechanical link rewrite, and the new m0 quest for the intermittent api_swift failure.
- Queue call:
queue.yml'sbuildjob now callskixel-ai/rust2/.github/workflows/queue-build.yml@main. That file exists onmainand is aworkflow_callworkflow. No workflow gates ongithub.repository_owner, and thegithub.repositoryuses innightly.ymlandqueue.yml'sreportjob pick up the new owner on their own. - Manifests and bug URL:
repositoryindriver,ffi,go, andts, plusBUG_REPORT_URLindriver/src/rustc.rs, now namekixel-ai/rust2. - Link rewrite:
git grep moq-dev/rust2finds nothing at the head. Themoq-dev/moqandmoq-dev/questreferences that remain are correct, because those repositories did not move:flake.nix's quest input,bench/build/corpus.toml,ts/fixtures/model/Cargo.toml, and the queue watcher comment inqueue.yml. quest/m0/swift-gives-up.md: I checked the diagnosis against the code and both races it names are real:- Empty closure:
Pollable.pollinffi/runtime/rt.swiftstarts the Task and then loadsdoneagain.Within::pollinffi/fixtures/api/src/lib.rspolls the inner future before it checksleft. So an empty closure that finishes in that window makeswithin(0) {}returnOk(()). - Single drain: the check in
ffi/tests/api.swiftreadsthrewafter oneq.drain(). The check above it usesuntil { q.drain(); ... }instead.
- Empty closure:
claude-opus-5-5 | 𝕏
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.

rust2 moved from
moq-devtokixel-aion 2026-11-12.Changes
queue.ymlcallskixel-ai/rust2/.github/workflows/queue-build.yml@main. kixel-ai'srust2-queuerunner group will admit only that ref.repositoryin the driver, ffi, go and ts manifests, and the driver's bug report URL, namekixel-ai/rust2.moq-dev/rust2tokixel-ai/rust2across the README files and quests. Links tomoq-dev/moqandmoq-dev/quest, which did not move, are unchanged.No workflow gates on the repository owner, so nothing else depended on the old name.
Public API
None.
Caused by
No single PR. The repository transfer to kixel-ai.
Validation
just ci origin/mainpassed when the PR was opened. On re-validation at475201efit failed onlyapi_swift("futures" failed: Rust gives up on an async closure). That failure is pre-existing:just ffi test --test fixturesfailed it in 2 of 4 runs on this branch and 1 of 5 atmain7008d1d3, and it passes alone. The follow-up owns it.git grep moq-dev/rust2finds nothing.Deploy
Done on 2026-11-13: kixel-ai has the
rust2-queuerunner group, and nixos runs kixelated/nixos#66 and #67, withnixos-rust2-ciregistered in that group. A merge group runs this PR'squeue.yml, which calls main'skixel-ai/rust2copy ofqueue-build.yml.Follow-ups
api_swift's "Rust gives up on an async closure" check fails intermittently atmain; the quest fixes the test's timing. No open decisions.Models
Size: XS
Implementer: Claude Code, Claude Opus 5.5
Implementer: Claude Code, claude-opus-5-5 (iterate, XS)
(Written by Claude Opus 5.5)
🤖 Generated with Claude Code
Summary by CodeRabbit
Review
Rewritten by
quest reviewafter each round.Head: 058503f
Base: origin/main at 7008d1d
Reviewer: Codex, gpt-6.1-sol, medium effort
Session:
01a1d30a-15c2-7b23-bce7-d83d773286d6, round 3Score: 9/10,
The incremental change only refines the documented Swift test race, matches the relevant code, and introduces no concrete defects; builds and tests were not run as instructed.Findings: none
Reviewer: opencode, opencode-go/deepseek-v4.1-flash, high effort
Session:
ses_e2cf5d601ffeoVQrVit0lr7956, round 3Score: 10/10,
The plan now covers both the empty-closure race and the queued-resumption race, citing the relevant Pollable.poll and Within::poll behavior, so the earlier finding is fixed with no new defects.Findings: none
The last round's findings, at 47d1740:
quest/m0/swift-gives-up.md:18:The proposed drain loop does not fix the empty-closure race;The Plan now names the empty-closure race at `ffi/runtime/rt.swift`'s `Pollable.poll` and `ffi/fixtures/api/src/lib.rs`'s `Within::poll`, requires the closure to stay pending, and keeps the drain-until wait for the resumption race.