[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #10132 [Trac]: Trac Timeline broken

#10132: Trac Timeline broken
------------------------+-------------------
     Reporter:  bastik  |      Owner:  erinn
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:
    Component:  Trac    |    Version:
   Resolution:          |   Keywords:
Actual Points:          |  Parent ID:
       Points:          |
------------------------+-------------------

Comment (by bastik):

 I think it is commit c27dc313c0ead935bbc71e8b92938fe4a4b18168.

 What helped me to get to this conclusion is the 'Browse Source' thing of
 trac, (where I sent an email to the list asking for how to handle that
 thingy, but got no reply.) (I created a ticket to add the link to
 gitweb.tp.o back to the navigation, to have both.)

 I still don't know how to handle 'Browse Source', but it can do something.

 Here is the
 [https://trac.torproject.org/projects/tor/changeset/c27dc313c0ead935bbc71e8b92938fe4a4b18168/stem
 commit above viewed in the source browser] and for me it spits an error:


 {{{
 Trac detected an internal error:

 ValueError: need more than 0 values to unpack

 [...]

 The action that triggered the error was:

 GET: /changeset/c27dc313c0ead935bbc71e8b92938fe4a4b18168/stem
 }}}

 For comparison other commits like
 [https://trac.torproject.org/projects/tor/changeset/b1fb3e7a2cbbef029f483f084da98940844a3058/stem
 b1fb3e7a2cbbef029f483f084da98940844a3058 looks like this]. In fact all
 commits of that day, beside the one with an error, gets displayed fine. In
 order to check, replace the commit inside the URL. (If you pick an invalid
 one it will give you an error that the changeset number is invalid)

 Trac could have us told earlier which changesets made it unhappy. Since
 the error in the source browser tells what triggers the error, the
 timeline feature could have been equally nice.

 [https://gitweb.torproject.org/stem.git/commitdiff/c27dc313c0ead935bbc71e8b92938fe4a4b18168
 Gitweb shows it like that].

 It might be the case that this is because there is no description (not the
 header, but what's below) for what has changed or that there are two diffs
 for
 {{{
  'stem/__init__.py'
 }}}

 The first might not be the case since
 [https://gitweb.torproject.org/tor.git/commitdiff/a7410c9199e58bd6c5ff131a994f8e02ccb42b91
 a Tor commit has no description as well]. I haven't found a commit with
 diff1 and diff2, yet. That might be the cause.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10132#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs