Error with trac

[Travis Scrimshaw]

I'm getting the following error anytime I try to attach a new branch to a ticket which previously didn't have one (in particular #12453 and #9280):

Trac detected an internal error:

TypeError: 'unicode' object is not callable

There was an internal error in Trac. It is recommended that you notify your local Trac administrator with the information needed to reproduce the issue.

To that end, you could  a ticket.

The action that triggered the error was:

POST: /ticket/9280

------------------------------------

Any ideas?

Thanks,

Travis

[Frédéric Chapoton]

I have the same problem with #15550. Quite displeasant.

Frédéric

[John Cremona]

I have a variation: I successfully pushed a new commit to #15554, then
went onto trac to enter the commit hash manually, but get the error
message

Oops…

Trac detected an internal error:

CalledProcessError: Command '['git',
u'--git-dir=/srv/git/repositories/sage.git', 'log', '--oneline',
u'3472a854df051b57d1cb7e4934913f17f1fef820',
'^8527d9fecac247012d1bf4dd843edffff90344e3', '^develop']' returned
non-zero exit status 128

There was an internal error in Trac. It is recommended that you notify
your local Trac administrator with the information needed to reproduce
the issue.

To that end, you could a ticket.

The action that triggered the error was:

POST: /ticket/15554
----------------

Shame -- just when I was beginning to enjoy the new development process a lot!

John

> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+...@googlegroups.com.
> To post to this group, send email to sage-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/groups/opt_out.

[John H Palmieri]

Yes, same for me with #14993. Any ideas what to do about it?

  John

[Volker Braun]

Its a bug in our trac plugin. I'm pretty sure Andrew will fix it when he has some time ;-)

[R. Andrew Ohana]

Yes, sorry. I'll try to look into this sometime this weekend.

--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
To post to this group, send email to sage-...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.

--

Andrew

[Travis Scrimshaw]

In case it's helpful, I was able to set the branch field before I pushed the branch to trac (with a ticket set at "new").

[R. Andrew Ohana]

Ok, the issue should hopefully be fixed now.

On Fri, Dec 20, 2013 at 7:41 AM, John Cremona <john.c...@gmail.com> wrote:

I have a variation: I successfully pushed a new commit to #15554, then
went onto trac to enter the commit hash manually, but get the error
message

Although in your case, you haven't actually pushed to the branch yet. I've added a nop (instead of error) if the commit field is invalid (this should only happen if someone enters the commit field manually -- which no one should ever have to do).

--

Andrew

[John Cremona]

Please tell me what to do -- checkout that branch again locally and do
another sage- dev push?

John

>
> --
> Andrew

[Volker Braun]

If you have pushed it then it is on our git server. You can just manually add a comment "I pushed branch X to git" until this is fixed.

[Travis Scrimshaw]

Works for me now. Thank you Andrew.

John, 

   Since it's been pushed to trac, all you need to do is manually set the "branch" field with the name of the branch (which you can see by running "git branch" [or sage -git branch if you don't have git installed] anywhere in the sage folder).

Best,

Travis

[John Cremona]

The branch field was already set and still is (see
http://trac.sagemath.org/ticket/15554), which is why I was little
puzzled by Volker's comment.

If you or someone could actually verify that that ticket is in a state
ready for reviewing, that would be helpful. Comparing with my other
recent one at #15556, there is a difference: both the Branch and
Commit field are filled in but after the branch name there is no
"Commits" link.

John

>
> Best,
> Travis