nspcc-dev / nspcc-dev/neofs-node
Warn user about using default config values in log
Open
Nobody has claimed this yet.
enhancement
I3
S4
U4
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
In case when some config value is unset/incorrect, neofs-node and neofs-ir application uses default value. It'd be nice to see this in application log.
Contributor guide
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 configuration parsing and default-value handling in the neofs-node and neofs-ir application entry points, then inspect how those applications write logs. Done means each fallback caused by an unset or incorrect configuration value is identifiable in the application log for both applications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100