Repository navigation
chore(quest): plan the moq pin's way past moq-wasm and moq-tokio's recursion limit #396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| # [S] Waiting: moq-tokio within the recursion limit | ||
|
|
||
| ## Goal | ||
|
|
||
| `just ffi moq` exports moq's `main` again. [moq-dev/moq#7032](https://github.com/moq-dev/moq/pull/7032) | ||
| made moq-tokio's `tokio::spawn` of `moq_net::time::run` overflow the trait solver's | ||
| recursion limit proving `Send`, a future-compat lint on the exporter's nightly that the | ||
| recipe denies so a later nightly cannot break the export. Until moq fixes it, the | ||
| exporter's moq pin cannot move past it and misses moq's later API. | ||
|
|
||
| Check: on the exporter's nightly, in a moq checkout, | ||
| `RUSTFLAGS="-D recursion_depth_exceeding_limit" cargo check -p moq-tokio`. Advance it with a | ||
| quest in moq. | ||
|
|
||
| ## Plan | ||
|
|
||
| Once it passes on moq's `main`, bump the exporter's `moq_rev` and update the config to what | ||
| `just ffi census` then refuses. | ||
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| # [M] Translate moq-net without moq-wasm | ||
|
|
||
| ## Goal | ||
|
|
||
| `just ts moq` and `just ts census` translate moq-net from moq's `main`, and the translator | ||
| and the exporter share one moq pin again ([#390](https://github.com/moq-dev/rust2/pull/390) | ||
| holds until then). moq dropped WASM in | ||
| [moq-dev/moq#7475](https://github.com/moq-dev/moq/pull/7475), and with it moq-wasm, which | ||
| picked the browser's randomness for moq-net's `rand` and `uuid` on wasm32. Without it, | ||
| getrandom and uuid refuse to build there, so the translator's moq pin cannot move past it. | ||
|
|
||
| ## Plan | ||
|
|
||
| The browser's randomness is a platform boundary, so the driver may pick it for a stock | ||
| crate, as a wasm32 binary would. Prefer what getrandom and uuid document for wasm32 over a | ||
| stand-in crate. | ||
|
|
||
| `just ts bench`'s `moq-wasm package` row has no source past that pin either: decide with | ||
| the maintainer whether it goes, or stays on the last revision with moq-wasm. The | ||
| [model's](/quest/m2/ts-model/README.md) comparison against moq's WASM build may change | ||
| with it. |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Script executed:
Repository: moq-dev/rust2
Length of output: 8746
Script executed:
Repository: moq-dev/rust2
Length of output: 45668
Script executed:
Repository: moq-dev/rust2
Length of output: 27764
Script executed:
Repository: moq-dev/rust2
Length of output: 4622
Web query:
moq-dev moq pull 7475 remove moq-wasm getrandom uuid wasm32Result:
Clarify the shared moq pin before bumping it.
The plan says to bump "the exporter's
moq_rev", but no exporter-specific pin exists inffi/. The exporter takes its default checkout from the translator's pin. Following the plan as written moves the translator to moq'smaintoo, where its wasm32 build fails.Suggested clarification
Add this to the plan in
quest/m1/ffi-export/recursion-limit.md, replacing line 17: