Wasmtime GitHub notifications bot (Jan 27 2024 at 00:25): Wasmtime GitHub notifications bot (Jan 27 2024 at 00:25):jameysharp opened PR #7832 from jameysharp:profiler-self-serve to bytecodealliance:main:
This is a proof of concept for #7666, but needs quite a bit of polish before merging.
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Jan 27 2024 at 00:30):jameysharp commented on PR #7832:
If anyone has suggestions on how to do this better I'd be interested to hear them. In particular, I'm not happy with how many crate dependencies I had to add to the Wasmtime CLI to make this work.
Currently this PR reflects just enough hacking together of pieces to prove that #7666 is possible, so I'm not looking for review on small details, just the big picture design questions.
Wasmtime GitHub notifications bot (Jan 27 2024 at 01:41):tschneidereit commented on PR #7832:
An alternative approach that shouldn't introduce any additional runtime dependencies would be to self-host this. I.e., to embed a wasi-http/proxy component that can load the profile from a pre-opened directory and serve it from the incoming-handler.
Such a component should be straightforward to run, and, after stripping, be quite small.
Last updated: Nov 22 2024 at 16:03 UTC