EMRY-010: Processor trait + pipeline thread #55
No reviewers
Labels
No labels
blocked
bug
compat
docs
documentation
duplicate
emry-cli
emry-core
emry-engine
emry-ingest
emry-py
emry-store
emry-tui
emry-web
enhancement
good first issue
gpu-compute
help wanted
hpc
infra
integrations
invalid
needs-design
P0-blocker
P1-core
P2-enhanced
P3-future
performance
pull-request
python
pytorch
question
rust
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
femboy/emry!55
Loading…
Reference in a new issue
No description provided.
Delete branch "emry-010-pipeline"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes EMRY-010 (#8). Branched off
main. First M1 (engine) issue.What
processor.rs:Processortrait (on_event(&mut self, &Event) -> Vec<DerivedMetric>) +DerivedMetric.pipeline.rs:Pipelinespawns one thread that drains the ring, forwards each raw event to theEventBus, runs processors, and emits derived metrics on a bounded channel.Shutdown contract
RunFinished→ graceful, ordered: all prior events drained before the thread exits.stop()/Drop→ prompt best-effort (flag checked each iteration), so Drop is bounded-time even under a flooding producer.Verification
./scripts/pre-commit-rust.shgreen: clippy-D warnings, 5 engine tests, pipeline.rs 98% lines, total 95.35%Review-driven changes