rename "up" to "starting" ?
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
Start by searching the repository for the "up" state and tracing where it is displayed or used. Check any related tests or command output, then determine the complete set of names that must change. Done means the intermediate state is consistently called "starting" and existing tests or checks still pass.
Written by the indexing model from the issue text.
Description
"up" is actually an intermediate state.
Any service that stays in this state long has something wrong with it.
I don't think "up" denotes this.
- Dominant language
- Python
- Stars
- 32
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from Yelp/pgctl
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
pgctl-poll-ready should either support cwd changes before it's exec'd, or warn when that happensOpenenhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 32/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CLIMADA-project/climada_python#1337 ·
Maintainers usually reply within 3 days
-
tail without reverseOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
8go/matrix-commander#233 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
documentation enhancement priority:high size:M
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Validate non-divisible effective batch sizes in the Unsloth LoRA backendPossibly taken @debesh-biswas claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100