-
Notifications
You must be signed in to change notification settings - Fork 35
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
Allow to enable wasmtime's profiling support #181
Allow to enable wasmtime's profiling support #181
Conversation
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.
thank you for your patience!! this looks great to me.
i have one very small style nit below, but this mechanically all looks correct. ✨
lib/src/lib.rs
Outdated
pub use wasmtime::ProfilingStrategy; | ||
pub use {error::Error, execute::ExecuteCtx, service::ViceroyService, upstream::BackendConnector}; |
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.
style nit:
pub use wasmtime::ProfilingStrategy; | |
pub use {error::Error, execute::ExecuteCtx, service::ViceroyService, upstream::BackendConnector}; | |
pub use {error::Error, execute::ExecuteCtx, service::ViceroyService, upstream::BackendConnector, wasmtime::ProfilingStrategy}; |
(this may need to get formatted)
This enables wasmtime's builtin profiling support. https://docs.wasmtime.dev/examples-profiling.html
68700a4
to
92f35af
Compare
Thank you for your review! Could you review again? |
can do! rerunning now... 💭 |
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.
✨ thanks again for adding this! how nifty 🔬
NB: this is 0.3.0 because breaking changes were introduced in #181.
NB: this is 0.3.0 because breaking changes were introduced in #181.
Fix #180.