TimelyDataflow / TimelyDataflow/differential-dataflow
Trace imports are invisible
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3k
- Forks
- 211
- Avg merge
- 10h 42m
- Merged PRs (30d)
- 34
Description
No events are emitted that can be used to piece together where an imported trace came from, TraceAgents manage their data internally and .import() uses the source operator to create an entirely new source, so there's no ChannelsEvent linking the two streams nor any sort of differential event that links them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating TraceAgent and the implementation of .import(), then inspect how the source operator emits events and how ChannelsEvent represents stream relationships. Determine the intended event or differential-event linkage for imported traces; done means trace provenance can be reconstructed from emitted events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100