Opened 7 years ago

Closed 6 years ago

#1146 closed defect (fixed)

Peer review files out of sync with svn repository

Reported by: lewisb@… Owned by: proofek
Priority: high Component: PeerReviewPlugin
Severity: major Keywords:
Cc: alexhalf@… Trac Release: 0.10

Description (last modified by proofek)

As an example of this bug, a particular directory in the subversion repository attached to our trac system has the following structure:


The top-level directory (JichuExample) has a revision number of 4 (because it was renamed). Everything below it has a revision number of 3.

When I create a new peer review using this file, it picks up the revision number as 3, not 4, and I can find no way to change this. The result is that when people go to input their review comments, instead of displaying the source code file, they receive this error:

"Internal Error

No node /JichuExample/jichu/core/playdescriptors/ at revision 3"

Attachments (1) (750 bytes) - added by proofek 6 years ago.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 7 years ago by sontek

  • Owner changed from Team5 to djeebus
  • Severity changed from normal to major

comment:2 Changed 6 years ago by anonymous

  • Priority changed from normal to high

comment:3 Changed 6 years ago by anonymous

  • Cc alexhalf@… added

comment:4 Changed 6 years ago by alexhalf@…

I have the same problem.

comment:5 Changed 6 years ago by proofek

  • Description modified (diff)
  • Owner changed from djeebus to proofek
  • Status changed from new to assigned

comment:6 Changed 6 years ago by proofek

  • Resolution set to fixed
  • Status changed from assigned to closed

Now fixed. I hope it does the right thing now :)

Changed 6 years ago by proofek


Add Comment

Modify Ticket

as closed .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from proofek. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.