Logs may be unpaired when errors occur in runtime
Open
Nobody has claimed this yet.
bug
logging
- Dominant language
- Julia
- Stars
- 344
- Forks
- 79
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 27
Description
With the new timespan logging from #263, @log_finish is not guaranteed to be hit if the function it's being called in throws an error. We should implement a convenience macro that will put the @log_finish in a try ... finally block for us to ensure it always gets run.
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 reading the timespan logging introduced in issue #263 and locate the existing @log_finish usage in the runtime. The work is done when the convenience macro ensures @log_finish runs even when the wrapped function throws an error, using the requested try ... finally behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100