Closed GoogleCodeExporter closed 9 years ago
Wow, you are really exercising Gitblit!
The tickets really are deleted. For the FileTicketService they exist as files
in the repo dir. Deleting the repo recursively destroys everything, including
the ticket files. BUT. All tickets are indexed with Lucene. All queries are
executed against the Lucene index. This allows multiple persistence engines to
be implemented without designing a new query system for each one. The Lucene
index *should* be purged of those tickets when you delete the repo, but
evidently you have found a case where this is not true.
What you are seeing are shadows of your deleted tickets. They are built from
the pieces stored in the Lucene index. Just enough data is indexed to populate
the query pages - but these are not really the tickets. That is why when you
drill into the page you throw exceptions; you are trying to retrieve & display
a ticket which does not exist.
So the problem is: the Lucene ticket index is not being correctly purged on
repository deletion when using the FileTicketService.
Original comment by James.Mo...@gmail.com
on 12 Aug 2014 at 7:13
I forgot to follow up on this earlier but I did manage to clear Lucene's cache
following the directions you have provided at
http://gitblit.com/tickets_replication.html. It did clear up the tickets and
fix the crash on the "My Tickets" page.
Original comment by gib...@gmail.com
on 18 Aug 2014 at 3:52
The NPE fix has been pushed. But like I mentioned before, the real problem is
that the index was not properly purged on repository deletion.
Did you delete the repo with Gitblit or did you manually delete the repo?
Original comment by James.Mo...@gmail.com
on 8 Sep 2014 at 8:57
> Did you delete the repo with Gitblit or did you manually delete the repo?
I deleted the repository through the GitBlit interface. After I first
discovered the problem I then tried multiple ways of deleting it and recovering
it but the problem remained until I found the clear cache command.
Original comment by gib...@gmail.com
on 8 Sep 2014 at 9:17
Found the bug. Fix pushed to master.
Original comment by James.Mo...@gmail.com
on 8 Sep 2014 at 10:08
v1.6.1 released
Original comment by James.Mo...@gmail.com
on 20 Oct 2014 at 9:36
Original issue reported on code.google.com by
gib...@gmail.com
on 18 Jul 2014 at 7:35