Skip to content
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

Merged
merged 4 commits into from
Aug 12, 2024

Conversation

kate-goldenring
Copy link
Contributor

  • Ensures compatibility with containerd-shim-spin which already inits a tracing subscriber
  • Bumps to latest Spin dependencies

src/lib.rs Outdated Show resolved Hide resolved
- Ensures compatibility with containerd-shim-spin which already inits a tracing subscriber
- Bumps to latest Spin dependencies

Signed-off-by: Kate Goldenring <kate.goldenring@fermyon.com>
Signed-off-by: Kate Goldenring <kate.goldenring@fermyon.com>
@kate-goldenring
Copy link
Contributor Author

kate-goldenring commented Jul 29, 2024

@radu-matei can you give this a review -- I don't have the perms to add reviewers

Signed-off-by: Kate Goldenring <kate.goldenring@fermyon.com>
fibonacci1729
fibonacci1729 previously approved these changes Aug 1, 2024
src/lib.rs Outdated
Comment on lines 208 to 213
self.handle_mqtt_event(
&component_id,
msg.payload().to_vec(),
msg.topic().to_owned(),
)
.await?;
Copy link
Contributor

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.

Copy link
Contributor

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.

Copy link
Contributor Author

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 <kate.goldenring@fermyon.com>
@karthik2804 karthik2804 merged commit 8d3e0c2 into spinkube:main Aug 12, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants