incorrect implementation of the increment_var
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What's going wrong?
The increment_var is implemented incorrectly.
How could we reproduce this issue?
- create an HTTP server
- make the server listen to port, which will be read from an environment variable
- define the said environment variable to be a string in the
ecosystem.config.js. E.g.:SERVER_PORT: "9090" - set the increment_var to 'SERVER_PORT' in the
ecosystem.config.js - run
pm2 start ecosystem.config.js - look at logs to see the SERVER_PORT being set to values like
90901,909011,9090111, etc.
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
Reproduce the issue with an HTTP server and the described ecosystem.config.js settings, focusing on increment_var and SERVER_PORT. Trace where PM2 applies increment_var, then verify that repeated starts produce numerically incremented port values rather than concatenated strings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100