This repository was archived by the owner on Mar 24, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 167
Support async in lucet-wiggle, and switch lucet-wasi to use tokio #655
Merged
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
b703729
vendor wiggle and wasi-common crates from alexcrichton/new-api
pchickey f4fd840
port lucet-wiggle & lucet-wasi to ctx syntax changes from wiggle
pchickey 42aa068
lucet-wiggle: wip adding async
pchickey 90914b6
lucet-wiggle: start fixing
pchickey 1142a1b
lucet-wasi: replace test suite with atoms_async; fix async execution
pchickey b23baed
lucet-wiggle: split out an integration macro just like wasmtime
pchickey 26a7f54
lucet-runtime-internals: fix wiggle dep
pchickey 42e64c8
lucet-wasi: delete generate subcrate, use lucet_wiggle::lucet_integra…
pchickey f4dea56
root cargo stuff
pchickey a6fb34b
rustfmt
pchickey 463a632
benchmarks: wasi benchmark requires tokio now
pchickey a6a8aab
lucet-wasi-fuzz: use tokio instead of rayon
pchickey b628bb9
rustfmt
pchickey 622e050
lucet-wiggle: run post_hook after ctx borrow has been returned.
pchickey 0756fbd
wasi-common build.rs: use CARGO_MANIFEST_DIR instead of cwd
pchickey a47a79d
wasmtime-new-api: add README breadcrumbs
pchickey 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
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
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,6 @@ | ||
| fn main() { | ||
| // wasi-common's links & build.rs ensure this variable points to the wasi root: | ||
| let wasi_root = std::env::var("DEP_WASI_COMMON_19_WASI").unwrap(); | ||
| // Make it available as WASI_ROOT: | ||
| println!("cargo:rustc-env=WASI_ROOT={}", wasi_root); | ||
| } |
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
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.
Could these be brought in via submodule instead of directly vendored? It would make potential security updates etc easier to apply.
Also, has this vendored code been reviewed in its home context?
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.
It potentially could be, but I intend for this to be short-lived enough that it doesn't matter. I am expecting it to land the main repo in a few weeks, so I didn't think it was worthwhile to add a submodule and delete it.
Yes, I have reviewed it in its home context, but not formally signed off yet.
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.
Gotcha. Can we leave some breadcrumbs to help apply any fixes that might be made before the formal sign-off? Like a marker of what git revision it's based off, and which branch/PR to watch over in
wasmtime?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.
Good idea, I've added this now.