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

dev/next: log router output #2308

Merged
merged 10 commits into from
Dec 17, 2024
Merged

dev/next: log router output #2308

merged 10 commits into from
Dec 17, 2024

Conversation

loshz
Copy link
Contributor

@loshz loshz commented Dec 17, 2024

Similar to the legacy implementation, this PR logs output from the running router binary.

@svc-apollo-docs
Copy link
Collaborator

svc-apollo-docs commented Dec 17, 2024

✅ Docs Preview Ready

No new or changed pages found.

@loshz loshz marked this pull request as ready for review December 17, 2024 14:56
@loshz loshz requested a review from a team as a code owner December 17, 2024 14:56
Comment on lines 46 to 53
match level {
"INFO" => tracing::info!(%message),
"DEBUG" => tracing::debug!(%message),
"TRACE" => tracing::trace!(%message),
"WARN" => write!(f, "{} {}", warn_prefix, &message)?,
"ERROR" => write!(f, "{} {}", error_prefix, &message)?,
"UNKNOWN" => write!(f, "{} {}", unknown_prefix, &message)?,
_ => {}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like there's some sort of due diligence I could suggest to make sure the level we're setting is right (based on what's in the router, which I've sure you've looked at), but it's sort of escaping me right now; the only thing that sort of worries me is the catch-all at the bottom not emitting anything (but maybe it's better to emit nothing than to emit a bunch of "warning! no level set!" or whatever)

Copy link
Contributor

@dotdat dotdat Dec 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even though this is the same as the original implementation
Maybe this should be _ => write!(f, "{} {}", unknown_prefix, &message)??

@aaronArinder
Copy link
Contributor

whoa, this got weird after having new commits merged; going to leave the approval, but not totally sure about all the new stuff (going to assume it's alright, but re-request a review if you want a sanity check)

@dotdat dotdat enabled auto-merge (squash) December 17, 2024 18:41
@dotdat dotdat merged commit 9e9f25d into main Dec 17, 2024
28 of 30 checks passed
@dotdat dotdat deleted the loshz/ROVER-251 branch December 17, 2024 18:57
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.

4 participants