Fossil Forum
Post: Check-in doesn't appear in file history
Hi all :)
I added a commit that was aborted due to my computer losing power (I just did "fossil commit" again after reboot and it was as if the commit was never done, just like it should be), this might be related to this case, but maybe not… I don't remember which commit it was.
If you look at this changeset: https://fossil.kd2.org/paheko/info/c1add484cf7f7f35
You'll see that src/include/lib/Paheko/API.php has been modified on 2026-08-03.
But this change doesn't appear in the history of the file here: https://fossil.kd2.org/paheko/finfo?name=src/include/lib/Paheko/API.php&m&ci=tip
I didn't shun anything this year so far.
I tried "fossil rebuild" but same result. I also tried the last trunk version of Fossil.
How do I get the commit back in the file history, and how can I know if other changes have become "missing"?
Thanks! Z
At your check-in c1add484cf7f7f35, the API.php file changes from version [d348c35b6d] to version [cb8b04f0e9]. Click on the link to the "to" version. On that page, at the top, in the file description you see a link to [check-ins using]. Click on that link and it will show you all of the check-ins that use the "to" version of your file.
Scroll down to the transition from 2026-08-02 to 2026-08-03. You can see that when you originally created that particular version of API.php, it eventually got merged into "next-stable" and then on the next check-in it was changed. The vertical dotted line on the trunk rail shows that there were some other check-ins that did not contain that exact version of the file. But later, at 2026-08-03T21:54, you made another change that restored the original version of API.php.
Thus the history of API.php version cb8b04f0e9 is disjoint and somewhat confused. And so when trying to show the history of that file, the graph might not be intuitive. This is why it is not displaying as you expect. The per-file timeline shows the first time that a particular version of a file appears in the check-in graph, but subsequent appearances.
The graph at https://fossil.kd2.org/paheko/timeline?from=624094390a&to=c1add484cf&v shows the sequence of changes for which API.php was different. You can see that API.php changed on the first check-in past the yellow one, and changed again on the blue check-in. That second change on the blue check-in apparently exactly undid the changes made on the prior one.
Thank you for the reply.
I was under quite some stress, being on holidays and having to fix a bunch of security issues that were pouring in from AI reports… not the best circumstances to make good code :(
Did you mean "The per-file timeline shows the first time that a particular version of a file appears in the check-in graph, but NOT subsequent appearances."?
If so, if I understand correctly the commit doesn't appear because it reverted a previous change, and the new version is identical to a previous one that is already in the list?
So yes it's not very intuitive as I was expecting to see all changes of that file, as the page title is "History of file src/include/lib/Paheko/API.php". Not seeing the commit there, I thought something was wrong inside Fossil.
If the commit is correctly in Fossil, and this is just a graph hickup, it's better, but still confusing.
Both fossil timeline -p src/include/lib/Paheko/API.php and fossil finfo src/include/lib/Paheko/API.php commands shows the "missing" commit, so I would have expected that the web page would do the same.
Z