nspcc-dev / nspcc-dev/neofs-dev-env
`make down/basic` does not stop morph
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 10
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
After #212 there is a new target in the Makefile: (up|down)/bootstrap. It has been added to every up/* but not to all the down/* targets.
As a result down/basic does not return a state after the up/basic. It confused me a little and was not expected of me: every local run was made using the same morph state without any cleaning. Not sure if it is something that we want to have in our makefile. Mb it is a kinda feature and allows caching morph b/w runs.
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 in the Makefile and compare the up/* and down/* targets, especially up/basic and down/basic, to see how the bootstrap target is handled. Run the up/basic then down/basic sequence and verify whether the morph state is cleaned up as expected; check the related down targets for consistent behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100