DUNE-DAQ / DUNE-DAQ/fdreadoutlibs
TAs are still being sent out after stop_trigger_sources
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 3
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 5
Description
This was causing issues for the TC maker trying to drain_dataflow in some tests when iomanager was refusing to end callback processing due to continuous arrival of messages.
Contributor guide
No contributing guide indexed for this repository
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 tracing the stop_trigger_sources and drain_dataflow paths, including the iomanager callback-processing behavior described in the issue. Reproduce the test scenario where continuous messages prevent draining, then verify that TAs are no longer sent after stop_trigger_sources and callback processing can finish.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100