Skip to content

fix: add peer address to connection logs and fix audiogain f32 type#485

Merged
srperens merged 1 commit intomainfrom
fix/connection-logging-and-audiogain
Apr 10, 2026
Merged

fix: add peer address to connection logs and fix audiogain f32 type#485
srperens merged 1 commit intomainfrom
fix/connection-logging-and-audiogain

Conversation

@srperens
Copy link
Copy Markdown
Collaborator

Summary

  • HTTP request logging: Add TraceLayer with ConnectInfo<SocketAddr> so all REST API requests log method, path, and peer address automatically
  • WebSocket peer logging: Add ConnectInfo extractor and tracing span per connection — all WS log lines include peer=ip:port
  • AudioGain panic fix: audioamplify element expects gfloat (f32) for the amplification property but was given f64, causing a panic on block creation

Test plan

  • Start server and verify HTTP requests show peer address in logs
  • Connect WebSocket client and verify connect/disconnect logs show peer
  • Create an AudioGain block and verify it no longer panics

🤖 Generated with Claude Code

Log client IP:port for all HTTP requests (TraceLayer) and WebSocket
connections (tracing span) so connections can be identified in the
console. Fix audiogain panic where audioamplify expects gfloat (f32)
but was given gdouble (f64).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@srperens srperens merged commit a0dc7fc into main Apr 10, 2026
7 checks passed
@srperens srperens deleted the fix/connection-logging-and-audiogain branch April 10, 2026 11:51
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