[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):

 Replying to [comment:4 erinn]:
 > bastik,
 >
 > You seem pretty good at this.

 I saw this bug and reported it, because it could have been something that
 sticks around longer. I tried to look into it and see what it takes to
 show the error(s). It was some testing of combinations, where luckily the
 only thing that triggered it involved 'stem' and was only 'stem' (instead
 of some odd combination).

 I was about to close this, before I tried to go back more days than the
 default 5. No "investigation" was made since my last reply to this ticket.
 Mostly because I don't know what could be wrong. So, I wouldn't call
 myself good at this, but I hope to have been helpful.

 >I tried to figure out what was in stem's repository that was making trac
 so angry but I haven't figured it out yet. While searching for more info
 it became clear that the git plugin is in some way at fault, combined with
 some kind of odd commit... but I don't know where!


 I can have a look, but don't think I'll have any clue what's wrong.

 >Is there anything I can do to help you figure it out?

 This would require some knowledge or clue about what could cause this, on
 my end. So, currently there would be nothing that would help, I think.

 Since this bug doesn't trigger for people visiting the default timeline,
 since it should now only occur if one increases the number of days the
 timeline goes back, the bug is not that annoying, though the reason should
 be found (or its cause) in order to prevent it from appearing again at a
 later point.

 My plan (for tomorrow, I guess) will be to figure out on which day the bug
 triggers and what commits have been made to 'stem' on that day. Then
 compare the commits with each other, then maybe with one from the next day
 since there's no commit that triggers the error.

 If you got some ideas how to approach this, please let me know.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10132#comment:5>
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