NASA-AMMOS / NASA-AMMOS/AIT-Core
Add logging to UTC Leapsecond handling
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Python
- Stars
- 56
- Forks
- 35
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 3
Description
The leapsecond load / processing is a bit opaque at the moment. Adding a few logs in the process would help clear up what's going on when AIT boots up and processes the data file or downloads updates.
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 locating the UTC leap-second loading and processing paths used when AIT boots, including the data-file and update-download flows. Review how those paths currently report activity, then add logs that make processing and update behavior observable; done means the relevant lifecycle steps are logged without changing handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100