Bazaar GTK+ Frontends

the viz screws up when opening a branch with no revisions

Bug #173698 reported by Daniel Schierbeck
14
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
Undecided
Unassigned
Bazaar GTK+ Frontends
Invalid
Low
Unassigned

Bug Description

When opening the viz with an empty branch, the following traceback is returned:

Traceback (most recent call last):
  File "/home/daniel/.bazaar/plugins/gtk/viz/treeview.py", line 234, in populate
    broken_line_length)
  File "/home/daniel/.bazaar/plugins/gtk/viz/linegraph.py", line 52, in linegraph
    generate_revno=True)
  File "/usr/lib/python2.5/site-packages/bzrlib/tsort.py", line 187, in merge_sort
    generate_revno).sorted()
  File "/usr/lib/python2.5/site-packages/bzrlib/tsort.py", line 410, in __init__
    parents = self._graph.pop(branch_tip)
KeyError: 'pop(): dictionary is empty'
dev> bzr viz > ~/traceback.txt
Traceback (most recent call last):
  File "/home/daniel/.bazaar/plugins/gtk/viz/treeview.py", line 234, in populate
    broken_line_length)
  File "/home/daniel/.bazaar/plugins/gtk/viz/linegraph.py", line 52, in linegraph
    generate_revno=True)
  File "/usr/lib/python2.5/site-packages/bzrlib/tsort.py", line 187, in merge_sort
    generate_revno).sorted()
  File "/usr/lib/python2.5/site-packages/bzrlib/tsort.py", line 410, in __init__
    parents = self._graph.pop(branch_tip)
KeyError: 'pop(): dictionary is empty'

Furthermore, the "ancestry graph is loading" bar does not go away.

Revision history for this message
Jelmer Vernooij (jelmer) wrote : Re: [Bug 173698] the viz screws up when opening a branch with no revisions

This works a little bit better now but you still get a traceback on the
console.

  status triaged
  importance low
--
Jelmer Vernooij <email address hidden> - http://samba.org/~jelmer/
Jabber: <email address hidden>

Changed in bzr-gtk:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Olivier Berger (olivierberger) wrote :

"Jelmer Vernooij" : Looks like more details would have been helpfull, as exact traceback you experience now...

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Olivier: Seems pointless, it's trivial to reproduce.

Revision history for this message
Olivier Berger (olivierberger) wrote :

Pointless... unless one needs to check if the message is the same as one reported in another ticket to try and do QA administrative work on bugs...

Just my 2 cents, as my problem was found elsewhere anyway.

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

I don't see the point in a traceback if the situation in which the bug exists is clearly defined.

The same backtrace doesn't necessarily mean the same bug.

This bug actually appears to've already been fixed, btw.

Revision history for this message
Szilveszter Farkas (phanatic) wrote :

This was fixed in Bazaar, so I've set it as Invalid for bzr-gtk.

Changed in bzr-gtk:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.