[forge:site-support:#1344] seems like it might be related/same issue. If not, let me know and I'll break it out into a new ticket.
The code tree view of the PrettyOS project does not work. It shows wrong commit for head and - what is even worse - it doesn't show most of the files in the repository (in fact, it shows only one file, keyboard.c).
We upgraded PrettyOS project to Allura yesterday. We received two mails from sourceforge. The last one says: "Your source code repositories are currently being migrated to the new setup. You will receive another email when that import is complete." We haven't received the promised mail so far, but SVN access seems to work. I guess that there happened some problem causing tree view to be corrupted and which is probably the reason for not receiving that mail one day after upgrade.
I can't reproduce the empty TreeDocs on my sandbox and in production, deleting them and viewing the page to rebuild them populates them correctly, so it appears to be an intermittent issue and / or race condition.
The change in allura:cj/5171 should be more resilient to the call to the SVN tool failing as well as race conditions between multiple processes hitting the non-existant node at the same time, but I have no real way to test it other than verifying that it still works in the common case.
I couldn't find any other place that a TreeDoc (or Tree) instance would be created for an SVN repo.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
[forge:site-support:#1344] seems like it might be related/same issue. If not, let me know and I'll break it out into a new ticket.
eg. https://sourceforge.net/p/prettyos/code/1392/tree/trunk/Source/kernel/
allura:cj/5171
I can't reproduce the empty TreeDocs on my sandbox and in production, deleting them and viewing the page to rebuild them populates them correctly, so it appears to be an intermittent issue and / or race condition.
The change in
allura:cj/5171
should be more resilient to the call to the SVN tool failing as well as race conditions between multiple processes hitting the non-existant node at the same time, but I have no real way to test it other than verifying that it still works in the common case.I couldn't find any other place that a
TreeDoc
(orTree
) instance would be created for an SVN repo.Also,
RepoObject.upsert()
is poorly named, as it is actually a safe insert, but it's used all over the place, so I didn't rename it.