Skip to content

feat: add CTFS trace format support#74

Open
zah wants to merge 2 commits into
mainfrom
ctfs-format-support
Open

feat: add CTFS trace format support#74
zah wants to merge 2 commits into
mainfrom
ctfs-format-support

Conversation

@zah

@zah zah commented Apr 7, 2026

Copy link
Copy Markdown
Member

Summary

  • Handle TraceEventsFileFormat::Ctfs in all match statements (streaming, like Binary)
  • trace.ct filename extension for CTFS output
  • "ctfs" format string accepted in config/env
  • Path dependencies on codetracer-trace-format crates (for Ctfs variant)

Set CODETRACER_TRACE_FORMAT=ctfs to produce .ct CTFS container traces.

Test plan

  • cargo check passes
  • just test with CTFS format (needs Linux CI)

🤖 Generated with Claude Code

zah and others added 2 commits April 7, 2026 12:52
Add TraceEventsFileFormat::Ctfs handling:
- events.rs: CTFS is streaming (same as Binary, no partial flush)
- output_paths.rs: CTFS uses trace.ct filename extension
- filesystem.rs: accept "ctfs" format string from config/env
- Cargo.toml: switch to path deps for trace-format crates

Recorders can now produce .ct CTFS container traces by setting
CODETRACER_TRACE_FORMAT=ctfs or passing format in config.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
CTFS is now the default trace format for the Python recorder.
Streaming writes flush events incrementally, enabling live replay.

- formats.py: DEFAULT_FORMAT = TRACE_CTFS
- session.py: updated docstring
- Other formats (binary, json, binaryv0) remain available via config

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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