You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When a user encounters a version mismatch with the gateway, the warning message gets cluttered by tracing metadata appended directly after the instructions:
Version incompatibility with gateway
Your client version: 0.1.72
Gateway version: 0.1.73
To fix this, update your Freenet client:
cargo install --force freenet --version 0.1.73
Or if building from source:
git pull && cargo install --path crates/core, direction: "outbound"
at C:\Users\Administrator\.cargo\registry\src\...\connection_handler.rs:747
The , direction: "outbound" and source location appear on the same line as the instructions, making the message hard to read.
Reported by user "dredd" on Matrix.
Approach
Remove extraneous tracing fields (peer_addr, direction, message) from this specific log call. The error message itself is user-facing and contains all the necessary information - the extra metadata adds no value and clutters the output.
The warning now simply logs the error, which produces a clean multi-line message without trailing metadata.
Testing
This is a cosmetic logging change with no behavioral impact
Remove extraneous tracing fields (peer_addr, direction) from the version
mismatch warning. The error message itself is user-facing and contains
instructions for updating - extra metadata from tracing cluttered the output.
Before:
```
Version incompatibility with gateway
Your client version: 0.1.72
Gateway version: 0.1.73
...
Or if building from source:
git pull && cargo install --path crates/core, direction: "outbound"
at C:\Users\...\connection_handler.rs:747
```
After: Clean multi-line message without trailing metadata.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <[email protected]>
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
When a user encounters a version mismatch with the gateway, the warning message gets cluttered by tracing metadata appended directly after the instructions:
The
, direction: "outbound"and source location appear on the same line as the instructions, making the message hard to read.Reported by user "dredd" on Matrix.
Approach
Remove extraneous tracing fields (
peer_addr,direction, message) from this specific log call. The error message itself is user-facing and contains all the necessary information - the extra metadata adds no value and clutters the output.The warning now simply logs the error, which produces a clean multi-line message without trailing metadata.
Testing
[AI-assisted - Claude]