‘.’ is not recognized

infinite-circle · July 29, 2019, 3:23pm

Hello, I have been trying to make a commit but I get this error

score: 60 initial, 120 final, 60 progress.
global-rank: 4871 initial, 4769 final, 102 progress.
national-rank: 0 initial, 0 final, 0 progress.
effort: 7.2 hours during immersion, productivity 8.33 points/hour.
Please add rules to your commitlint.config.js
- Getting started guide: https://git.io/fhHij
- Example config: https://git.io/fhHip [empty-rules]
  found 1 problems, 0 warnings
  (Need help? -> https://github.com/conventional-changelog/commitlint#what-is-commitlint )

husky > commit-msg hook failed (add --no-verify to bypass)

I did npm install

$ npm install

training@1.0.0 postinstall D:\fluid\training
./ci-scripts/commitlint-conf.sh

‘.’ is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! training@1.0.0 postinstall: ./ci-scripts/commitlint-conf.sh
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the training@1.0.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

infinite-loop · July 29, 2019, 7:57pm

Looks like you’re running the command from Windows, you need Linux, or at least a shell to do this.

infinite-circle · July 29, 2019, 8:54pm

Running in Ubuntu and getting the same error

infinite-loop · July 29, 2019, 10:20pm

Can you please attach logs of the npm install command in ubuntu?

Also, make sure you have curl installed.

hermit-purple · July 29, 2019, 10:30pm

You should also check the path where you are running the npm command, if you don’t have a config file (such as package.json) in the same folder the command will not succeed, make sure you are running it at the root of the repo.

roaring-lamport · July 29, 2019, 10:37pm

Tried to emulate the OP’s situation in a vanilla ubuntu docker container, got the same error.
Installing curl fixed it.
Perhaps not redirecting stderr to /dev/null or first testing for which curl would have shown that was the problem?
curl $COMMITLINT_RULES_URL > $COMMITLINT_RULES_NAME 2> /dev/null

gitlab.com

fluidattacks/writeups/blob/master/ci-scripts/commitlint-conf.sh

#!/usr/bin/env bash

#This scripts download commitlint's configuration files

COMMITLINT_RULES_NAME='commitlint.config.js'
COMMITLINT_PARSER_NAME='parser-preset.js'
COMMITLINT_BASE_URL='https://gitlab.com/fluidattacks/default/raw/master/commitlint-configs/writeups'
COMMITLINT_RULES_URL="$COMMITLINT_BASE_URL/$COMMITLINT_RULES_NAME"
COMMITLINT_PARSER_URL="$COMMITLINT_BASE_URL/$COMMITLINT_PARSER_NAME"

curl $COMMITLINT_RULES_URL > $COMMITLINT_RULES_NAME 2> /dev/null
curl $COMMITLINT_PARSER_URL > $COMMITLINT_PARSER_NAME 2> /dev/null

infinite-circle · July 30, 2019, 1:36pm

Yes, the problem was with Curl, and I had proxy configuration so the curl connected to localhost instead of going out to the internet

roaring-lamport · July 30, 2019, 2:40pm

If the issue is solved, please mark the thread as such.