Apache Allura™

Forge software for hosting software projects

Brought to you by: alexluberg, brondsem, ccruz, deshani, and 11 others

#4886 dosbox svn repo displaying "no files" [ss473]

Milestone: v1.0.0

Status: closed

Owner: Cory Johns

Labels: p2 (24) sf-2 (994)

Component: General

Reviewer: nobody

Updated: 2015-08-20

Created: 2012-09-08

Creator: Chris Tsai

Private: No

[forge:site-support:#473]

https://sourceforge.net/p/dosbox/code-0/3797/tree/

I can get a checkout just fine, so as far as I can tell, the repo itself is working properly, but dosbox's svn repo browser shows "-- no files --" for rev 3791 and newer (at time of writing, rev 3797 is the latest).

Possibly related, when I first checked it, it seemed to be stuck "analyzing" so I gave it a manual refresh (just a regular one, not a clean refresh, I can't do those). The subsequent analysis finished, but now we're in this state.

Related

Tickets: ~~#4886~~

Discussion

Dave Brondsema - 2012-09-10

milestone: limbo --> forge-backlog
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2012-09-10

Full refresh didn't fix it.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2012-09-11

labels: support, p2 --> support, p2, 42cc
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2012-09-12

Created #167: [#4886] dosbox svn repo displaying "no files" (2cp)

Related

Tickets: ~~#4886~~

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2012-09-12

status: open --> in-progress
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2012-09-12

I've imported that repo and I can browse all revisions just fine.

I'll try to investigate the code to find bug that leads to this behavior, but so far I have no ideas whats going wrong.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2012-09-12

I am starting a re-import from this project's old classic repo (http://dosbox.svn.sourceforge.net/svnroot/dosbox/) to see if that will fix it in Allura.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2012-09-12

That still did not work. Igor, you can try using the Admin page (on your development environment) to do an SVN import using URL http://dosbox.svn.sourceforge.net/svnroot/dosbox/ and it seems like that should duplicate the problem for you.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2012-09-13

I imported repo using that URL and still can browse all revisions.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2012-09-17

Maybe importing from old repo (http://dosbox.svn.sourceforge.net/svnroot/dosbox/) to an empty, freshly installed svn-repo tool will fix this in Allura?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2012-09-17

I tried that too, but it didn't work. Maybe because the pre-existing data in mongo for the other tool messed it up (since scm data is shared across tools). I can confirm that on a clean Allura instance the import works fine, so it is a data issue and not a bug in the code.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2012-09-19

Seems like "No files" happens when TreeDoc for the given revision has empty trees_ids, blob_ids and other_ids.

But existing TreeDoc's does not updated when running repository import or refresh from the UI. (Repository.refresh always get called with all_commits=False)

Is there a way to run repo refresh with updating all related TreeDoc's CommitDoc's and other metadata? Seems like scripts/refresh-all-repos.py with --all and --clean options for given project/tool should do this. I think this should fix the problem, but I can't test it locally, because I can't reproduce the problem on a clean Allura instance.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2012-09-21

labels: support, p2, 42cc --> support, p2

milestone: forge-backlog --> forge-oct-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2012-09-21

size: --> 2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Cory Johns - 2012-09-25

assigned_to: Cory Johns
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Chris Tsai - 2012-09-26

labels: --> p2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Cory Johns - 2012-09-27

status: in-progress --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Cory Johns - 2012-09-27

Cleared the bad repo_tree cache record and it is displaying correctly now.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.