Skip to content

Conversation

@MasterPtato
Copy link
Contributor

Changes

Copy link
Contributor Author

MasterPtato commented Jun 10, 2025

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more


How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

Comprehensive update to logging levels across the guard infrastructure to improve production log signal-to-noise ratio and maintainability.

  • Downgraded routine operations (WebSocket connections, request handling) from info to debug in packages/edge/infra/guard/core/src/proxy_service.rs
  • Upgraded configuration failures to warn level and enhanced error formatting with ?err syntax in packages/edge/infra/guard/server/src/tls.rs
  • Removed unused imports (tracing::warn, regex::Regex) from request context and util files
  • Standardized error variable naming from e to err across multiple files for consistency
  • Improved structured logging patterns and upgraded routing timeouts from warn to error in proxy service

7 files reviewed, 2 comments
Edit PR Review Bot Settings | Greptile

Comment on lines +139 to +141
tracing::error!("{} connection error: {}", port_type_str, err);
}
info!("{} connection dropped: {}", port_type_str, remote_addr);
tracing::debug!("{} connection dropped: {}", port_type_str, remote_addr);
Copy link

Choose a reason for hiding this comment

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

style: Consider adding structured logging fields here to make connection errors more easily parseable. Use the ?err syntax like other error logs in this file.

Suggested change
tracing::error!("{} connection error: {}", port_type_str, err);
}
info!("{} connection dropped: {}", port_type_str, remote_addr);
tracing::debug!("{} connection dropped: {}", port_type_str, remote_addr);
if let Err(err) = conn.await {
tracing::error!(?err, "{} connection error", port_type_str);
}
tracing::debug!("{} connection dropped: {}", port_type_str, remote_addr);

Comment on lines 1379 to 1387
},
Some(Err(e)) => {
Some(Err(err)) => {
// Error receiving message from client
error!("Error receiving message from client: {}", e);
error!("Error details: {:?}", e);
tracing::debug!(?err, "Error receiving message from client");
tracing::debug!(?err, "Error details");
// Signal shutdown to other direction
let _ = shutdown_tx.send(true);
break;
},
Copy link

Choose a reason for hiding this comment

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

style: Duplicate error logging removed - the first log line already includes error details through ?err

Suggested change
},
Some(Err(e)) => {
Some(Err(err)) => {
// Error receiving message from client
error!("Error receiving message from client: {}", e);
error!("Error details: {:?}", e);
tracing::debug!(?err, "Error receiving message from client");
tracing::debug!(?err, "Error details");
// Signal shutdown to other direction
let _ = shutdown_tx.send(true);
break;
},
},
Some(Err(err)) => {
// Error receiving message from client
tracing::debug!(?err, "Error receiving message from client");
// Signal shutdown to other direction
let _ = shutdown_tx.send(true);
break;
},

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Jun 10, 2025

Deploying rivet with  Cloudflare Pages  Cloudflare Pages

Latest commit: 84aaf41
Status:🚫  Build failed.

View logs

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Jun 12, 2025

Deploying rivet-hub with  Cloudflare Pages  Cloudflare Pages

Latest commit: 84aaf41
Status:🚫  Build failed.

View logs

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Jun 12, 2025

Deploying rivet-studio with  Cloudflare Pages  Cloudflare Pages

Latest commit: 84aaf41
Status:🚫  Build failed.

View logs

@MasterPtato MasterPtato changed the base branch from 06-07-feat_db_sh_for_workflows to graphite-base/2580 June 12, 2025 21:21
@MasterPtato MasterPtato changed the base branch from graphite-base/2580 to 06-07-feat_db_sh_for_workflows June 12, 2025 22:30
@MasterPtato MasterPtato force-pushed the 06-07-feat_db_sh_for_workflows branch from 2bdeefd to fba1301 Compare June 12, 2025 23:04
@MasterPtato MasterPtato force-pushed the 06-10-chore_guard_fix_log_levels branch from b3aa8b4 to 2e8e98f Compare June 12, 2025 23:04
@MasterPtato MasterPtato changed the base branch from 06-07-feat_db_sh_for_workflows to graphite-base/2580 June 13, 2025 18:10
@MasterPtato MasterPtato changed the base branch from graphite-base/2580 to 06-07-feat_db_sh_for_workflows June 13, 2025 20:43
@MasterPtato MasterPtato force-pushed the 06-10-chore_guard_fix_log_levels branch from 2e8e98f to 4a380a5 Compare June 13, 2025 22:55
@MasterPtato MasterPtato force-pushed the 06-07-feat_db_sh_for_workflows branch from fba1301 to 84f7df4 Compare June 13, 2025 22:55
@NathanFlurry NathanFlurry force-pushed the 06-07-feat_db_sh_for_workflows branch from 84f7df4 to cfc30cf Compare June 15, 2025 20:24
@NathanFlurry NathanFlurry force-pushed the 06-10-chore_guard_fix_log_levels branch from 4a380a5 to 84aaf41 Compare June 15, 2025 20:24
@NathanFlurry NathanFlurry force-pushed the 06-07-feat_db_sh_for_workflows branch from a3cf488 to 6ce34ef Compare June 20, 2025 19:18
@NathanFlurry NathanFlurry force-pushed the 06-10-chore_guard_fix_log_levels branch from c33d751 to 5b30dea Compare June 20, 2025 19:18
@graphite-app
Copy link
Contributor

graphite-app bot commented Jun 20, 2025

Merge activity

  • Jun 20, 7:19 PM UTC: MasterPtato added this pull request to the Graphite merge queue.
  • Jun 20, 7:20 PM UTC: CI is running for this pull request on a draft pull request (#2630) due to your merge queue CI optimization settings.
  • Jun 20, 7:22 PM UTC: Merged by the Graphite merge queue via draft PR: #2630.

graphite-app bot pushed a commit that referenced this pull request Jun 20, 2025
<!-- Please make sure there is an issue that this PR is correlated to. -->

## Changes

<!-- If there are frontend changes, please include screenshots. -->
@graphite-app graphite-app bot closed this Jun 20, 2025
@graphite-app graphite-app bot deleted the 06-10-chore_guard_fix_log_levels branch June 20, 2025 19:22
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.

1 participant