Keeping diagnostic going after all sources are completed?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 574
- Forks
- 104
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
I have a program that reads a PsiStore and does calculation on it. The program is pretty slow and end up taking way longer (~180 seconds) than the actual PsiStore stream length (~30 seconds). The PsiStore Importer finish publishing messages after the 30 second mark and the diagnostic stop around 50 second mark. The last message won't be created until the 300 second mark. Is there a way to keep diagnostic running till the end instead of just stopping at 50 sec?
Here's a screenshot of PsiStudio illustrating my problem. The first row is the messages from diagnostic.
I made some changes to Visualization to make the time go beyond originating time interval. The changes can be seen here: https://github.com/CMU-TBD/psi/commit/389298d04ff5f8624949119e1130530299cfdceb
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 comparing the PsiStore Importer, diagnostic, and Visualization behavior described in the issue with the referenced Visualization commit. Trace why diagnostic stops around 50 seconds while the final message is delayed until 300 seconds; done means diagnostic continues until all source messages are processed and the behavior is verified with the reported timing scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- stream-processing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100