-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tiny oversight for development builds and pm2 report due to semver check (temp fix included) #3695
Comments
shikhir-arora
changed the title
Tiny oversight for development builds and pm2 report due to semvar check (temp fix included)
Tiny oversight for development builds and pm2 report due to semver check (temp fix included)
Jun 5, 2018
Good catch. |
No problem, I figured it was worth noting because development builds could be prone to more 'need' of the |
Merged
wallet77
added a commit
that referenced
this issue
Jun 7, 2018
inerc
pushed a commit
to inerc/pm2
that referenced
this issue
Feb 11, 2020
…k with alpha/beta versions
inerc
pushed a commit
to inerc/pm2
that referenced
this issue
Feb 11, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What's going wrong?
Just a small oversight perhaps, in the development branch currently at
3.0.0-alpha1
,pm2 report
will throw a defined error:[PM2][ERROR] You need to update your Daemon, please type $ pm2 update
.This is obviously not what we want to do and it won't change the result.
This is due to the semvar check here at line 111.
How could we reproduce this issue?
3.0.0-alpha1
) the normal way:Run
pm2 report
after verifying withpm2 --version
that your version is the development/alpha build.The error described above will occur.
Temporary Fix
I just fixed this quickly by changing the check on the above mentioned line to the following, which will parse out the build and is valid for any build that would be checked. The only case where it would return true where you may want it to return false is if someone used
2.6.0-alpha
or any-prerelease
of 2.6.0. That's very unlikely, and even if they were running that, it would fail anyways as it's still the same issue with the semver format.Current snippet:
Changed to the following to fix:
You probably don't need this, but I will follow the guideline (I did get
pm2 report
working, as mentioned above).If this is intentional, I apologize. I looked around and didn't see any other complaints about it on the issues tracker/Git blame, so I thought I'd bring it up since
pm2 report
seems like it'd have use on development builds for actual issues. 🙂Supporting information
The text was updated successfully, but these errors were encountered: