Bug: Timeline in html-report shows "Invalid Date" #201
Comments
|
I have also the same problem in the html report For your information, when I trigger a simple report (not an html report), I get this result with {
"gitRepoPath": "/Users/user/Projects/foobar",
"gitFilePath": "apps/name/openapi.yaml",
"filename": "openapi.yaml",
"dateGenerated": "2025-04-29T08:39:37+02:00",
"reports": [
{
"reportSummary": {
"paths": {
"totalChanges": 1,
"breakingChanges": 0
}
},
"changes": [
{
"breaking": false,
"change": 3,
"changeHash": "FE28eVXDAjzr4UzHw95YdKCK2QOIhJK85U8dq2cQ5oQ=",
"changeText": "object_added",
"context": {
"newColumn": 3,
"newLine": 710
},
"new": "/flow/foobar",
"original": "",
"property": "path"
}
],
"commitDetails": {
"commitHash": "33cf524",
"message": "feat(): add new route for test",
"author": "Username",
"authorEmail": "[email protected]",
"committed": "2025-04-29T08:31:17+02:00",
"changeReport": null
}
}
]
}and a Is there any other information I can provide to help you find the problem? Thanks for this wonderful tool! |
|
Could you provide a screen shot? I cannot replicate this locally. this is what I see
|
|
also, I will fix the changeReport thing, it's a glitch and should not be there. |
|
Hi @daveshanley , here are the screenshots. 
Another thing, when I trigger the command : As problem may come from commit message, here it is in text for easy copy for testing on your side : |
|
This is a strange bug man. Why would one date work, and another not, even when formatted with the same RFC. |
|
Yes strange indeed. |
Trying to debug #201 The date parsing is handled by a “parse anything’ lib, which is great, but also confusing as there should never be an invalid date. When trying to re-run this command locally. The ‘||’ delimiter was being interpreted as ‘or’ instead of a format string. I changed the delimiter and upgraded it to a quoted string. Lets see if this solves it.
|
Can you try this branch? https://github.com/pb33f/openapi-changes/tree/v0.0.80 I am trying to track this glitch down, I think this may be the root of it, I can't re-create it locally. |
|
Yes, I guess you've found the rootcause ! I've performed a test on the 
Then I try on the 
|
|
Well, by curiosity, I've checked the change you've done on the branch Here is a debug session to help you, I may have found something First of all, I think you should revert 6dd07a1 Because, when adding some println in "Wed, 7 May 2025 15:32:40 +0000|||d61f07b|||chore(release): version 1.16.0|||semantic-release-bot|||[email protected]"
"Wed, 7 May 2025 11:29:59 +0200|||8e4e694|||feat(RET-32527): Auto generation of OpenAPI specs for both ECS (searcher / exporter-full)|||Jerome Despatis|||[email protected]"Then, after this commit reverted, I've tested again with some logs: As you can see, in my case, here are the conversions performed, and how it appears on the html report:
As you can see, the date after parsing is some kind of weird, the timezone appears twice, As a result when the timezone is utc (for example I cannot help much more because I can do other tests of course Hope this helps |
|
I have kind of the same issue I think. I don't know if it helps, but I am sitting in Germany, @jdespatis seems to sit in France, so there might be an issue with non-US citizens? |
When looking a a single commit in the html report, I see the date at the top left:
07 Apr 2025 10:10:40 CEST.In the timeline window however, I only see
Invalid Dateover every commit.My
LANGisen_US.UTF-8. Any other information that might be useful?The text was updated successfully, but these errors were encountered: