control-net/vr-retreat

Handle Background Worker's exceptions

Open

#30 opened on Dec 29, 2021

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)C# (1 fork)auto 404
Backendgood first issuehelp wantedmaintenance

Repository metrics

Stars
 (6 stars)
PR merge metrics
 (PR metrics pending)

Description

Summary

In case the background worker encounters and error, it should output it into its log instead of closing.

Alternatively the log file name could be appended with -failed.log to better recognize this scenario.

A general try/catch could work. Alternatively we can hook into the UnhandledException event of the runtime to be a bit more sure.

The exception should also be printed in the log itself.

Notes

Careful about exceptions that are coming from failed attempt at logging.

Want to work on this issue?

❤️ Amazing! Let us know in the comments bellow so that we can assign this issue to you. 🎉

No stress, though, feel free to ask for help with any clarifications or problems you may encounter along the way. We're here to help.

Contributor guide

Research direction
Implement a try/catch block in the background worker or hook into the UnhandledException event to log exceptions instead of closing the application. Ensure logging itself does not throw exceptions.
Tech stack
csharp
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75