On 2017-02-13 12:33, Clemens Heuberger wrote:
> It is my subjective observation that timeouts on patchbots have become more
> frequent. For instance, for ticket
> https://patchbot.sagemath.org/ticket/22340/
> two patchbots failed due to timeout,
I also noticed this to become more frequent.
W
I just did it, it seems to work.
Thanks
S.
* Daniel Krenn [2017-02-20 20:47:03]:
On 2017-02-20 19:24, VulK wrote:
Dear All,
I just found a bug I can't really reproduce in any simpler way than the
one I have here. I did not open a ticket yet on this because I would
like to have a simpler way
On 2017-02-20 19:24, VulK wrote:
> Dear All,
> I just found a bug I can't really reproduce in any simpler way than the
> one I have here. I did not open a ticket yet on this because I would
> like to have a simpler way to explain the issue first. Any idea?
Yes, a bit above from the line where your
Dear All,
I just found a bug I can't really reproduce in any simpler way than the one I
have here. I did not open a ticket yet on this because I would like to have a
simpler way to explain the issue first. Any idea?
{{{
sage: LQ = LaurentPolynomialRing(QQ, 'x0, x1, x2, y0, y1, y2, y3,
On Tue, Feb 14, 2017 at 4:32 PM, Michael Orlitzky wrote:
> On 02/14/2017 10:19 AM, Erik Bray wrote:
>>
>> Add explicit imports to the test, for example:
>>
>> TESTS::
>>
>> sage: from foo import foo
>> sage: foo()
>> True
>
> Same error: name 'foo' is not define
On 2017-02-14 15:54, Michael Orlitzky wrote:
I have a few thousand failing doctests like that where I can't simply
remove the __init__.py file.
Adding __init__.py has specific semantics in Python: it means that your
directory (which was a random bunch of Python files) is now a package.
For a
@bennigoetz reported the same problem in December 2016 :
https://github.com/ipython/ipython/issues/9816#issuecomment-258242213
For now, the only solution seems to go back to IPython 4.x ...
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsub
On 02/20/2017 10:00 AM, Travis Scrimshaw wrote:
> Could we get a little more context for your problem? In particular, is
> foo.py included in the Sage source tree or is it something that you are
> building separately? If it is the former, have you tried "from path.to.foo
> import bar", where the
A related issue as fixed in IPython in June 2016:
"Multi line paste not working anymore in 5.0 beta"
https://github.com/ipython/ipython/issues/9600
But it does seem to have fixed everything...
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To
Could we get a little more context for your problem? In particular, is
foo.py included in the Sage source tree or is it something that you are
building separately? If it is the former, have you tried "from path.to.foo
import bar", where the path is starting from $SAGE_ROOT/src?
Best,
Travis
O
On Saturday, February 18, 2017 at 4:31:04 PM UTC+1, William wrote:
>
>
> in SMC at least, if you try to paste in multiple
> lines it pastes in the first line and silently **ignores everything
> else**.
>
I have the same problem since Fall 2016 (major IPython upgrade?) when I use
tmux with
Ah, so not Bernstein-Gelfand-Gelfand then...
>
I would love to see microbadges on MO like this though.
--
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-dev
On Mon, Feb 20, 2017 at 04:32:32AM -0800, Volker Braun wrote:
> There is no general client request body size limit, this is a configuration
> setting for your wsgi server or reverse proxy that is in front of the
> patchbot. If you need help debugging this then post the relevant **server**
> log
There is no general client request body size limit, this is a configuration
setting for your wsgi server or reverse proxy that is in front of the
patchbot. If you need help debugging this then post the relevant **server**
log that shows the 413 being triggered.
On Thursday, January 26, 2017 a
On 2017-02-20 08:48, Thierry wrote:
Hi,
On Mon, Feb 20, 2017 at 08:32:18AM +0100, Jeroen Demeyer wrote:
On 2017-01-26 10:18, Daniel Krenn wrote:
Starting a patchbot results in the error below. Any ideas?
This issue makes it *impossible* for me to run a patchbot.
If anybody is able to fix th
Hi,
On 2017-02-20, Daniel Krenn wrote:
> On 2017-02-19 17:57, rjf wrote:
>> It might be comparing the real parts. What did you expect? Perhaps
>> Error "<" requires that both operands be members of the same ordered
>> field ??
>> Or perhaps just
>> False
>
> I, for sure, did not expect "True".
On 2017-01-08 07:21, Clemens Heuberger wrote:
>>> However, if I understand the code correctly, the patchbot should at least
>>> see
>>> the ticket and report
>>> "do not test if some author is not trusted"
>>> , which it does not in my case. It's simply not in the downloaded file, its
>>> not
17 matches
Mail list logo
