-
Notifications
You must be signed in to change notification settings - Fork 10
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
Use Spin telemetry crate #29
Use Spin telemetry crate #29
Conversation
kate-goldenring
commented
Jun 7, 2024
- Ensures compatibility with containerd-shim-spin which already inits a tracing subscriber
- Bumps to latest Spin dependencies
- Ensures compatibility with containerd-shim-spin which already inits a tracing subscriber - Bumps to latest Spin dependencies Signed-off-by: Kate Goldenring <[email protected]>
89e1202
to
013c45b
Compare
Signed-off-by: Kate Goldenring <[email protected]>
@radu-matei can you give this a review -- I don't have the perms to add reviewers |
Signed-off-by: Kate Goldenring <[email protected]>
src/lib.rs
Outdated
self.handle_mqtt_event( | ||
&component_id, | ||
msg.payload().to_vec(), | ||
msg.topic().to_owned(), | ||
) | ||
.await?; |
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.
I am not sure that the behavior here is the intended one. in case the guest returns an error, I think we will want to only log that error and continue the loop.
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.
Oh yeah good catch @karthik2804 . I forgot we did that to not return on an error.
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.
Wouldn't the error here come from the MQTT event source not the guest (Spin app)? I could see bubbling up the error as being useful to make the error more apparent to the user. But it does make sense to match existing behavior. It is now logging the error.
Signed-off-by: Kate Goldenring <[email protected]>