Fix the absolute/relative path weirdness when setting up WASI-based runner filesystems #3704
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.
This PR introduces a bunch of hacks and workarounds so the
WasiRunner
can run Python scripts and theWcgiRunner
can serve files from the host.I've also introduced a
TraceFileSystem
that can be useful when debugging filesystem operations, and fixed the#[tracing::instrument]
annotations on all our syscalls so they will actually log things like file fdescriptors (turns out#[tracing::instrument(..., fields(fd), ...)]
won't actually log thefd
variable).