Page 1 of 1

Updated today Force check errors

Posted: Wed Jan 16, 2019 8:55 pm
by dardack
2019-01-16 15:54:06 ERROR Git returned bad info. Are you sure this is a git installation? [fatal: ambiguous argument '%cr': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
]
2019-01-16 15:54:06 ERROR Error: None
2019-01-16 15:53:02 ERROR Git returned bad info. Are you sure this is a git installation? [fatal: ambiguous argument '%cr': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
]
2019-01-16 15:53:02 ERROR Error: None

Re: Updated today Force check errors

Posted: Wed Jan 16, 2019 8:59 pm
by dardack
OK I fixed that error by updating Git. Now in my logs i'm getting hundreds of:

2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1
2019-01-16 15:58:27 INFO i: 1

Re: Updated today Force check errors

Posted: Wed Jan 16, 2019 9:05 pm
by evilhero
OOopsie. That shouldn't have been in there (was used by me for debugging something else). Removed as of the newest development commit a few minutes ago (#4af50e4)