logger

Open
#48 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
observability

Research direction

The issue names no files, tests, or entry points. Start by locating the Python exception handlers and any existing logging configuration, then determine how caught exceptions should be recorded. Done means the required caught exceptions are logged consistently and the behavior is covered by tests.

Written by the indexing model from the issue text.

Description

include a logger to log all catched exceptions

Dominant language
Python
Stars
7
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FireDynamics/LEDSmokeAnalysis

All issues in FireDynamics/LEDSmokeAnalysis

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.