-
Notifications
You must be signed in to change notification settings - Fork 304
Display server version at startup when not running from git repository #1111
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
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-HANDLEBARS-173692
[Snyk] Fix for 1 vulnerable dependencies
I see a Travis CI failure is reported, but I don't know how to find out what is actually failing. |
Great, thanks! So, about the mechanics, you need to submit it to the 5.0.0 branch, so rebase on Then, it is a good idea to run |
Pretty weird you get errors, but now Travis is happy, so I am happy :-) I have rebased the PR, so what remains is just to resolve the conflict, which has happened in package-lock.json. Those are a nuisance, but just take what is in the |
I'm trying to get the tests to run in my local environment. As starting point, I got a local copy of release/v5.0.0, thus:
So I have:
At this point, I figure I ought to be able tu run the tests:
But I get a whole slew of errors reported, similar to what I was seeing before.
Here are just a few of the errors I'm seeing:
|
@gklyne what version of the |
@dmitrizagidulin
(and lots of other stuff.) |
Meanwhile I've pulled package-lock.json from the release/v5.0.0 branch to try and resolve the conflict:
|
Hmmm.. looks like I broke it again. |
@gklyne ok, yeah, so that's what's causing the issue. You're running standard 12.0 but solid-server and travis is running standard 8.6 or something. So your version is later & stricter, and the code base has not adjusted to it. |
@dmitrizagidulin Aha! I've downgraded to standard@8.6, and But
|
Hmmm... it looks as of most of the failures may be localhost lookup problems - aren't these set up as test fixtures/mocks/or something? |
Right, so, those can't be automatically set up by the fixtures, you have to edit those yourself. See: https://github.com/solid/node-solid-server#editing-your-local-etchosts |
@dmitrizagidulin that did it, thanks. I also had to stop a running solid server. Now all tests pass. It might be worth adding a link to the CONTRIBUTING file (in the bit that talks about making sure the tests pass before submitting a PR). |
OK, I now have a branch It appears I can't change this pull request to change the source branch (per https://stackoverflow.com/questions/44864448/git-change-the-source-branch-of-a-pull-request), so I propose to cancel this PR and start a new one with the new branch. |
@gklyne You can change the source branch of a PR by doing a |
Ack. Thanks. I was also trying to align my branches with solid versions. |
See #1110
This fix raises an error when the version information returned by running git is empty, thereby falling back to using package.json.
(I'm not very conversant with PR mechanics, so apologies if the form is wrong here.)