Skip to content

qlogwriter: add support for event_schemas in the trace header#5361

Merged
marten-seemann merged 1 commit intomasterfrom
qlogwriter-event-schemas
Oct 9, 2025
Merged

qlogwriter: add support for event_schemas in the trace header#5361
marten-seemann merged 1 commit intomasterfrom
qlogwriter-event-schemas

Conversation

@marten-seemann
Copy link
Copy Markdown
Member

@marten-seemann marten-seemann commented Oct 8, 2025

Depends on #5360.

@marten-seemann marten-seemann requested a review from Copilot October 8, 2025 13:52
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds support for event_schemas in the qlog trace header to specify which event schemas are used in the trace. The changes introduce an eventSchemas parameter to qlog file creation functions and ensure the event_schemas field is properly included in the JSON output when schemas are provided.

  • Modified qlog writer functions to accept event schemas as a parameter
  • Added EventSchema constant for QUIC event schema URN
  • Updated all callers to pass the QUIC event schema when creating connection traces

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
qlogwriter/writer.go Added eventSchemas parameter to file creation functions
qlogwriter/trace.go Added EventSchemas field to trace header and JSON encoding logic
qlogwriter/trace_test.go Updated tests to verify event_schemas field handling
qlog/qlog_dir.go Added EventSchema constant and updated DefaultConnectionTracer
qlog/benchmark_test.go Updated benchmark to include event schema parameter
interop/utils/logging.go Updated qlog creation to include event schema
integrationtests/tools/qlog.go Updated qlog creation to include event schema

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Comment thread qlogwriter/writer.go Outdated
@codecov
Copy link
Copy Markdown

codecov Bot commented Oct 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.97%. Comparing base (33af127) to head (5c94f18).
⚠️ Report is 1 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5361      +/-   ##
==========================================
- Coverage   83.04%   82.97%   -0.06%     
==========================================
  Files         156      156              
  Lines       18723    18736      +13     
==========================================
- Hits        15547    15546       -1     
- Misses       2563     2574      +11     
- Partials      613      616       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@marten-seemann marten-seemann force-pushed the qlogwriter-event-schemas branch from bbd4029 to 6058118 Compare October 8, 2025 13:54
@marten-seemann marten-seemann force-pushed the qlogwriter-event-schemas branch from 6058118 to 5c94f18 Compare October 8, 2025 14:22
@marten-seemann marten-seemann changed the base branch from qlogwriter to master October 8, 2025 14:33
@marten-seemann marten-seemann requested a review from Copilot October 9, 2025 04:06
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated no new comments.


Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@marten-seemann marten-seemann merged commit c26e86c into master Oct 9, 2025
17 checks passed
@marten-seemann marten-seemann deleted the qlogwriter-event-schemas branch October 11, 2025 05: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.

2 participants