Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
sage-devel
Home
About this group
Apply for group membership
Small bug in trac e-mail report
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Florent Hivert  
View profile  
 More options Mar 13 2010, 5:40 am
From: Florent Hivert <florent.hiv...@univ-rouen.fr>
Date: Sat, 13 Mar 2010 11:40:19 +0100
Local: Sat, Mar 13 2010 5:40 am
Subject: Small bug in trac e-mail report
Print | Individual message | Show original | Report this message | Find messages by this author
      Hi there,

There is a small bug in trac's automatic report by e-mails. On
    sage-combinat-commits@googlegroups.com
we just receive the following e-mail from trac (see [1] below)

> #8500: Add the set of TransitiveGroups
> -----------------------------+--------------------------------------------- -
> [...]
> -----------------------------+--------------------------------------------- -
> Changes (by newvalueoldvalue):

>   * status:  needs_review => needs_work
>   * author:  => Nicolas Borie
> [...]

The author should be nthiery and not newvalueoldvalue. You can find other
instance of this bug in eg. in [2],[3]. Is it known ? Should it be reported
somewhere ? Should I open a ticket about it ? Any idea where it is coming
from ? Is is sufficiently harmless so that it should be ignored ?

Florent, asking a lot ;-)

[1] http://groups.google.com/group/sage-combinat-commits/msg/fab9d1a41858...
[2] http://groups.google.com/group/sage-combinat-commits/browse_thread/th...
[3] http://groups.google.com/group/sage-combinat-commits/msg/b2f1ec556aab...


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Craig Citro  
View profile  
 More options Mar 13 2010, 1:11 pm
From: Craig Citro <craigci...@gmail.com>
Date: Sat, 13 Mar 2010 10:11:07 -0800 (PST)
Local: Sat, Mar 13 2010 1:11 pm
Subject: Re: Small bug in trac e-mail report
Print | Individual message | Show original | Report this message | Find messages by this author

> The author should be nthiery and not newvalueoldvalue. You can find other
> instance of this bug in eg. in [2],[3]. Is it known ? Should it be reported
> somewhere ? Should I open a ticket about it ? Any idea where it is coming
> from ? Is is sufficiently harmless so that it should be ignored ?

FWIW, I've seen this and complained in my head about it probably a
million times. I keep putting it off until I have time to sit down and
figure out whether it's us or trac itself, so I haven't done anything
about it -- but yes, it's known, yes, it's annoying, and yes, it
should be fixed. Maybe open a trac ticket saying someone should
determine the cause (us or trac) and fix it/file a more precise bug
report. Okay, I guess I'm not *quite* that lazy:

  http://trac.sagemath.org/sage_trac/ticket/8526

-cc


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Florent Hivert  
View profile  
 More options Mar 13 2010, 1:30 pm
From: Florent Hivert <florent.hiv...@univ-rouen.fr>
Date: Sat, 13 Mar 2010 19:30:44 +0100
Local: Sat, Mar 13 2010 1:30 pm
Subject: Re: [sage-devel] Re: Small bug in trac e-mail report
Print | Individual message | Show original | Report this message | Find messages by this author
      Hi Craig,

> > The author should be nthiery and not newvalueoldvalue. You can find other
> > instance of this bug in eg. in [2],[3]. Is it known ? Should it be reported
> > somewhere ? Should I open a ticket about it ? Any idea where it is coming
> > from ? Is is sufficiently harmless so that it should be ignored ?

> FWIW, I've seen this and complained in my head about it probably a
> million times. I keep putting it off until I have time to sit down and
> figure out whether it's us or trac itself, so I haven't done anything
> about it -- but yes, it's known, yes, it's annoying, and yes, it
> should be fixed.

Wow ! Asking google about "newvalueoldvalue" I only found 10 answers. So I
assumed it was new and only for our trac.

> Maybe open a trac ticket saying someone should determine the cause (us or
> trac) and fix it/file a more precise bug report. Okay,

So my first assumption is wrong but maybe my second is true...

> I guess I'm not *quite* that lazy:

>   http://trac.sagemath.org/sage_trac/ticket/8526

Thanks for doing it for me ;-)

Florent


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google