isce-framework / isce-framework/s1-reader
[New Feature]: use pyre journal for logging
Open
Nobody has claimed this yet.
enhancement
needs triage
- Dominant language
- Python
- Stars
- 34
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
Logging in s1-reader is inconsistent with logging in COMPASS
Describe the feature request
Use pyre journal to log errors and warnings.
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
No files or tests are named. Start by locating existing error and warning logging in s1-reader and reviewing how COMPASS uses pyre journal; done means the relevant logging is consistently handled through pyre journal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100