TritonDataCenter / TritonDataCenter/node-triton
`triton ls state=provisioning` doesn't filter on state
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 36
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 1
Description
It was returning state=running intss for me. It is possible that I had none in provisoining... in case that is a factor.
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 reproducing the issue with triton ls state=provisioning, then trace the triton ls state option through the CLI and filtering logic. Done means the command returns only provisioning instances and does not include running instances, including when no provisioning instances exist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100