Code maat is not parsing date in TFS log

Question

Code maat is not parsing date in TFS log

mauro2357 opened this issue 7 years ago · 6 comments

I am trying to execute code maat in TFS but i get the following error:

Invalid argument: Unsupported TFS Date Format: Thursday, December 21, 2017 9:26:46 AM
This is Code Maat, a program used to collect statistics from a VCS.
Version: 1.0-SNAPSHOT

This is the command i am using

java -jar code-maat.jar -l "C:\TFS\Loc\Dev\Satrack.Loc.Core\Domain\tfslog.csv" -c tfs -a revisions

And this is the tfs log i am using.

tfslog.txt

I checked and the date is in the locale that you recommend.

Thanks!

Answer 1 · 2018-01-10T17:47:02.000Z

This was my patch, I'll take a look at it!

Answer 2 · 2018-01-10T18:28:09.000Z

I am having difficulty reproducing this issue:
lein -run -l tfslog.txt -c tfs -a revisions
puts output that I'd expect, a list of files with a single revision each.

Is there any other information you have? Perhaps the previous entry in the TFS log is somehow throwing off the parsing grammar?

Answer 3 · 2018-01-10T19:31:41.000Z

This is the complete log i get in the console.

maat.txt

In this link is the jar i am using. https://drive.google.com/file/d/1sJeYRZqaAmz27ZTXzaS9npm6tLdZsHDC/view?usp=sharing
it was generated on 2018-january-2 with the code commited until that day on github.

I am running the program in windows 7 professional with the locale US

Thanks in advance

Answer 4 · 2018-01-10T20:15:48.000Z

Even that JAR is working as expected for me, and I'm wondering what could be causing a problem, it shouldn't be down in the system settings at this point, because the TFS log you shared is in the correct format. I'm wondering if somehow there's a grammar issue that's trickling down?

Have you confirmed you get the same behavior if you use the same tfslog.txt that you provided(and not your original CSV file)?

Answer 5 · 2018-01-10T21:39:14.000Z

I used the txt that i uploaded and the problem is the same. Does the program use environment variables or depend on a specific version of OS?

Answer 6 · 2018-01-10T23:01:40.000Z

It shouldn't be affected by anything like that, and even when I toggle my system's formats from en-us to no-no, this is still parsing as expected for me. Are you able to debug this and provide any additional info out of the exception that clj-time is throwing?