Every change of state logged in ONE FILE

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
django, python, sqlite
Domain
backend

Research direction

The payload names the logger_runner process, its stderr log files, and the django_gui_logmessage table in Django's sqlite database, but no source file for the state-change path. Start by finding where logger state and logger-manager mode changes are commanded, then decide whether to write them to a single dedicated file. Done means every commanded change appears in that one file with a readable "changed mode to <x>" line. The issue has no comments or maintainer input, so confirm the approach with maintainers before coding.

Written by the indexing model from the issue text.

Description

enhancement good first issue help wanted high priority

Is your feature request related to a problem? Please describe.
No problem.

Describe the solution you'd like
Every commanded change in any logger state or logger-manager mode to be logged in one file. This is useful for inclusion in the end-of-cruise data distribution.

Describe alternatives you've considered
Scripting something that would scour the sqlite database or the various log files and collect that data for me. But there's less information about the database than I thought. Kinda have to sort through the Django code and piece the information together, and while you can grep for "logger_runner" in the stderr files and sort, that isn't nearly as concise as just having something say "changed mode to ". I can select from "django_gui_logmessage" from Django's sqlite database, which is nice, I suppose.

Additional context
Add any other context or screenshots about the feature request here.

Dominant language
Python
Stars
57
Forks
30
Avg merge
3h 14m
Merged PRs (30d)
56

Getting set up

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 OceanDataTools/openrvdas

All issues in OceanDataTools/openrvdas

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.