Re: [sage-devel] ask.sagemath

[William Stein]

On Fri, Nov 10, 2017 at 12:48 PM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> Hopefully, you are unblocked. This is more than weird! Why on earth could
> you be blocked!? I will investigate in the logs.

Yes, I'm unblocked.  If anybody else is not using ask.sagemath due to
being blocked, don't hesitate to post...

>
>
> On 10/11/2017 21:26, William Stein wrote:
>>
>> Hi,
>>
>> I'm using "William Stein2 (karma: 2069, badges: ● 1)".   Please
>> unblock me.I'm not a spammer :-)
>>
>> William
>>
>> On Fri, Nov 10, 2017 at 11:50 AM, Vincent Delecroix
>> <20100.delecr...@gmail.com> wrote:
>>>
>>> which account are you using? "William Stein" (wst...@gmail.com) or
>>> "William
>>> Stein 2" (wst...@sagemath.com)? There is something weird with the second
>>> one.
>>>
>>> On 10/11/2017 20:39, William Stein wrote:


 Why is my account always blocked?

>>>
>>> --
>>> 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+unsubscr...@googlegroups.com.
>>> To post to this group, send email to sage-devel@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/sage-devel.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>>
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.



-- 
William (http://wstein.org)

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] ask.sagemath

[Vincent Delecroix]

Hopefully, you are unblocked. This is more than weird! Why on earth 
could you be blocked!? I will investigate in the logs.


On 10/11/2017 21:26, William Stein wrote:

Hi,

I'm using "William Stein2 (karma: 2069, badges: ● 1)".   Please
unblock me.I'm not a spammer :-)

William

On Fri, Nov 10, 2017 at 11:50 AM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:

which account are you using? "William Stein" (wst...@gmail.com) or "William
Stein 2" (wst...@sagemath.com)? There is something weird with the second
one.

On 10/11/2017 20:39, William Stein wrote:


Why is my account always blocked?



--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.






--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] ask.sagemath

[William Stein]

Hi,

I'm using "William Stein2 (karma: 2069, badges: ● 1)".   Please
unblock me.I'm not a spammer :-)

William

On Fri, Nov 10, 2017 at 11:50 AM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> which account are you using? "William Stein" (wst...@gmail.com) or "William
> Stein 2" (wst...@sagemath.com)? There is something weird with the second
> one.
>
> On 10/11/2017 20:39, William Stein wrote:
>>
>> Why is my account always blocked?
>>
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.



-- 
William (http://wstein.org)

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] problem with roots of a quadratic over a power series ring

[John Cremona]

Why does this not work:

sage: K. = PowerSeriesRing(QQ, 't', 5)
sage: R. = K[]
sage: F = y^2 + y - 2*t - 3*t^2 - t^3
sage: F.discriminant().sqrt()
1 + 4*t - 2*t^2 + 10*t^3 - 42*t^4 + O(t^5)

but

sage: F.roots()
---
TypeError Traceback (most recent call last)
...
TypeError: unable to convert Ideal (-2*t - 3*t^2 - t^3, 1, 1) of Power
Series Ring in t over Rational Field to a rational

while the quadratic formula works as it should:

sage: D = F.discriminant()
sage: sol = (-F[1]+D.sqrt())/(2*F[0])
sage: F(sol)
-4*t + 6*t^2 - 38*t^3 + O(t^4)

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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] ask.sagemath

[Vincent Delecroix]

which account are you using? "William Stein" (wst...@gmail.com) or 
"William Stein 2" (wst...@sagemath.com)? There is something weird with 
the second one.


On 10/11/2017 20:39, William Stein wrote:

Why is my account always blocked?



--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Coercion about finite field extensions, again

[Kwankyu Lee]

This is now

https://trac.sagemath.org/ticket/24195

I regard this behavior as a bug.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] p-adic factorization/root finding bug.

[David Roe]

Thanks.  Created https://trac.sagemath.org/ticket/24193
David

On Fri, Nov 10, 2017 at 3:08 AM, Simon Brandhorst 
wrote:

> {{{
> sage: f=x^22 + 9*x^21 + 16*x^20 - 92*x^19 - 408*x^18 - 144*x^17 +
> 2080*x^16 + 4096*x^15 + 128*x^14 - 8192*x^13 - 12800*x^12 - 18432*x^11 -
> 51200*x^10 - 131072*x^9 + 8192*x^8 + 1048576*x^7 + 2129920*x^6 - 589824*
> : x^5 - 6684672*x^4 - 6029312*x^3 + 4194304*x^2 + 9437184*x + 4194304
> :
> sage: f.factor()
> (x - 2)^6 * (x + 2)^8 * (x^8 + 5*x^7 + 16*x^6 + 40*x^5 + 88*x^4 + 160*x^3
> + 256*x^2 + 320*x + 256)
> sage: g=f.change_ring(Qp(2,200))
> sage: g.roots()
>
> [(1 + 2 + 2^3 + 2^4 + 2^5 + 2^7 + 2^8 + 2^10 + 2^11 + 2^12 + 2^15 + 2^16 +
> 2^19 + 2^20 + 2^22 + 2^28 + 2^31 + 2^32 + 2^38 + 2^39 + 2^40 + 2^41 + 2^43
> + 2^44 + 2^46 + 2^47 + 2^50 + 2^53 + 2^54 + 2^56 + 2^57 + 2^59 + 2^60 +
> 2^61 + 2^68 + 2^71 + 2^74 + 2^75 + 2^76 + 2^77 + 2^84 + 2^86 + 2^89 + 2^90
> + 2^94 + 2^95 + 2^97 + 2^100 + 2^106 + 2^107 + 2^110 + 2^112 + 2^113 +
> 2^118 + 2^119 + 2^124 + 2^126 + 2^127 + 2^128 + 2^132 + 2^135 + 2^141 +
> 2^143 + 2^145 + 2^146 + 2^147 + 2^148 + 2^149 + 2^150 + 2^151 + 2^152 +
> 2^155 + 2^160 + 2^162 + 2^165 + 2^166 + 2^168 + 2^170 + 2^171 + 2^173 +
> 2^174 + 2^176 + 2^177 + 2^180 + 2^181 + 2^183 + 2^184 + 2^185 + 2^187 +
> 2^189 + 2^190 + 2^191 + 2^192 + 2^193 + 2^194 + 2^195 + 2^196 + 2^197 +
> 2^198 + O(2^200),
>   1),
>  (2^2 + 2^3 + 2^6 + 2^7 + 2^8 + 2^10 + 2^11 + 2^12 + 2^13 + 2^14 + 2^17 +
> 2^18 + 2^20 + 2^23 + 2^24 + 2^28 + 2^29 + 2^33 + 2^34 + 2^36 + 2^39 + 2^40
> + 2^42 + 2^44 + 2^45 + 2^47 + 2^54 + 2^55 + 2^56 + 2^58 + 2^59 + 2^61 +
> 2^63 + 2^69 + 2^70 + 2^71 + 2^78 + 2^81 + 2^82 + 2^84 + 2^87 + 2^88 + 2^89
> + 2^90 + 2^91 + 2^93 + 2^95 + 2^99 + 2^100 + 2^101 + 2^102 + 2^103 + 2^104
> + 2^108 + 2^110 + 2^113 + 2^115 + 2^116 + 2^117 + 2^118 + 2^121 + 2^122 +
> 2^123 + 2^124 + 2^126 + 2^128 + 2^130 + 2^131 + 2^133 + 2^135 + 2^137 +
> 2^139 + 2^140 + 2^141 + 2^142 + 2^144 + 2^145 + 2^146 + 2^148 + 2^151 +
> 2^152 + 2^157 + 2^158 + 2^159 + 2^163 + 2^165 + 2^166 + 2^169 + 2^170 +
> 2^171 + 2^174 + 2^175 + 2^176 + 2^177 + 2^179 + 2^181 + 2^182 + 2^184 +
> 2^188 + 2^192 + 2^193 + 2^194 + 2^195 + 2^196 + 2^198 + O(2^200),
>   1)]
>
>
> }}}
>
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Development tasks

[Vincent Delecroix]

Hi,

The aim of the patchbot is to test trac tickets 
(http://trac.sagemath.org/) in order to help reviewers. Indeed, 
patchbots apply patches (formally these are git branches from 
https://git.sagemath.org/) and run the Sage testsuite (which are mostly 
doctests).


For Sage there is a pool of patchbots run by volunteers ("clients") and 
a sever (with a web interface at https://patchbot.sagemath.org/).


The way each individual client patchbot run is up to the user (there are 
several parameters that can be tuned). You can test a given ticket or 
ask the server for some tickets.


Vincent

On 10/11/2017 16:41, Andy Howell wrote:

Vincent,

That sounds interesting too. Years ago I deployed a buildbot for our
company, so I'm familiar with it. It has probably changed since then.

I thought that buildbot could used to apply patches.

Is the idea behind patchbot that it is simpler system dedicated to
trying out patches at the request of developers?

Thanks,

Andy


On 11/10/2017 02:25 AM, Vincent Delecroix wrote:

Dear Andy,

You could also help improving the patchbot (written in pure Python)

     https://github.com/sagemath/sage-patchbot

For example:

* fixing some false positive
* better support for testing of optional packages
* logs should not go in SAGE_ROOT/logs/patchbot/

Would you be interested?

Vincent

On 09/11/2017 14:40, Andy Howell wrote:

I've been using Sage on and off for a number of years, and am currently
using it while re-learning the calculus I took 35+ years ago. I'm
definitely the oldest in my class this time around!

I'm running the current dev version under Ubuntu 17.04. I have to move to
another laptop temporarily. The build on Ubuntu 17.10 is failing on
openBlas. I'll make another post about that issue.

I'm interested in helping out on Sage in some small way. I've had a look
through the trac list for beginners, but didn't see anything that was an
obvious fit for my skills.

I'm a c++ developer in my day job. I have done some python
development, and
ran a buildbot setup for awhile. I don't have the mathematical ability to
take on core issues. Something involving basic python, unit testing,
documentation etc would be a good fit.

I saw that there is work on supporting python 3. Is there more that needs
doing on that? Maybe more doctests? Documentation?

I'm looking for suggestions on where I can get started.

Thanks,

Andy






--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Development tasks

[Andy Howell]

Vincent,

That sounds interesting too. Years ago I deployed a buildbot for our
company, so I'm familiar with it. It has probably changed since then.

I thought that buildbot could used to apply patches.

Is the idea behind patchbot that it is simpler system dedicated to
trying out patches at the request of developers?

Thanks,

Andy


On 11/10/2017 02:25 AM, Vincent Delecroix wrote:
> Dear Andy,
> 
> You could also help improving the patchbot (written in pure Python)
> 
>     https://github.com/sagemath/sage-patchbot
> 
> For example:
> 
> * fixing some false positive
> * better support for testing of optional packages
> * logs should not go in SAGE_ROOT/logs/patchbot/
> 
> Would you be interested?
> 
> Vincent
> 
> On 09/11/2017 14:40, Andy Howell wrote:
>> I've been using Sage on and off for a number of years, and am currently
>> using it while re-learning the calculus I took 35+ years ago. I'm
>> definitely the oldest in my class this time around!
>>
>> I'm running the current dev version under Ubuntu 17.04. I have to move to
>> another laptop temporarily. The build on Ubuntu 17.10 is failing on
>> openBlas. I'll make another post about that issue.
>>
>> I'm interested in helping out on Sage in some small way. I've had a look
>> through the trac list for beginners, but didn't see anything that was an
>> obvious fit for my skills.
>>
>> I'm a c++ developer in my day job. I have done some python
>> development, and
>> ran a buildbot setup for awhile. I don't have the mathematical ability to
>> take on core issues. Something involving basic python, unit testing,
>> documentation etc would be a good fit.
>>
>> I saw that there is work on supporting python 3. Is there more that needs
>> doing on that? Maybe more doctests? Documentation?
>>
>> I'm looking for suggestions on where I can get started.
>>
>> Thanks,
>>
>> Andy
> 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Symbolic Matrix Calculus in Sagemath

[hashiromer621]

Thanks very much, the paper is quite helpful. 

On Thursday, November 9, 2017 at 10:54:10 PM UTC+5, rjf wrote:
>
>
> Asking for suggestions from the person(s) who will have to approve
> the result is always a good idea.
>
>
> I looked around some more for applications of matrix calculus, and
> do not see much evidence regarding my initial evaluation.  There
> seem to be some optimization and machine learning chat about
> this, but most relevant computations seem easy to do with mapping
> derivative functions over matrices.   If I've missed some deep and
> interesting uses and programs, and places where people were
> searching for programs to do such stuff as proposed in the wikipedia
> article --  my apologies.
>
>
> If you want to carry on more symbolic stuff, there's plenty to do,
> I think. 
>
> Here's a discussion of symbolic matrices that I wrote some time ago--
> https://people.eecs.berkeley.edu/~fateman/papers/symmat2.pdf
>
> It includes some survey-ish stuff, and some programs.   A simple
> symbolic question:  can you prove that transpose(transpose(A)) is
> equal to A,   knowing that A is  nXm but where n, m are
> unknown objects but assumed to be positive integers?
>
> RJF
>   actually, not a fan of coffee :)
>
>
>  
>
>
> On Wednesday, November 8, 2017 at 11:52:14 PM UTC-8, mforets wrote:
>>
>> Hello, 
>> also here's an open thread for symbolic support for matrices in the sympy 
>> project: https://github.com/sympy/sympy/issues/5858
>> Hence, seems to me that the answer to your (i) is "no".
>> I also found this interesting: 
>> http://www.matrixcalculus.org/matrixCalculus and 
>> http://www.math.uwaterloo.ca/~hwolkowi//matrixcookbook.pdf
>>
>> For (ii) and (iii), since your motivation is your university degree 
>> (getting credits and such), have you asked your local professor(s) for 
>> orientation? Then, I'm certain that here / on sympy you can find motivated  
>> "mentors" for your project (similarly to the successful GSOC -google summer 
>> of code- thing, right?).
>>
>>
>> El jueves, 9 de noviembre de 2017, 7:51:53 (UTC+1), Ralf Stephan escribió:
>>>
>>> Hello,
>>> Sage's symbolic support for matrices is limited. However, Sage contains 
>>> packages that may be used instead, like SymPy. For their matrix expression 
>>> / equation solving capabilities see
>>> http://docs.sympy.org/latest/modules/matrices/expressions.html
>>>
>>> http://docs.sympy.org/latest/modules/matrices/expressions.html#block-matrices
>>>
>>> Regards,
>>>
>>> PS please excuse rjf, he sometimes has probably had too much coffee
>>>
>>
>>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Why does the patchbot not test tickets that are determined to be "spkg" updates?

[Thierry]

On Fri, Nov 10, 2017 at 01:47:23PM +0100, Erik Bray wrote:
[...]
> I don't understand the issue here--if a package is a dependency of
> Sage then it will be built, right?  This only seems to apply to
> optional packages.

Yes. As far as i am concerned, optional packages are a very important part
of Sage, and they cause a nontrivial part of building issues for SDL
(precisely because they are barely tested on 32bit systems).

[...]
> Ah, well that's where my improved package uninstallation system comes
> in:  https://trac.sagemath.org/ticket/22510
> 
> This actually works very well in my testing so far, but getting the
> functionality merged is taking some time as there are some difficult
> prerequisites (e.g. https://trac.sagemath.org/ticket/22509).

Great initiative!

Ciao,
Thierry

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Why does the patchbot not test tickets that are determined to be "spkg" updates?

[Erik Bray]

On Fri, Nov 10, 2017 at 1:38 PM, Thierry
 wrote:
> On Fri, Nov 10, 2017 at 01:04:36PM +0100, Thierry wrote:
> [...]
>> But, if we want to add an option to let the patchbot install a new package
>> proposed by some ticket, after testing that ticket, the patchbot will be
>> in a different state than before to test other tickets, in this situation,
>> the patchbot will report possibly wrong false negative.
>
> A workaround for that (at least on decent OSes), would be to have a
> unionfs mechanism that adds a disposable layer mounted on $SAGE_ROOT/local
> and $SAGE_ROOT/src/build during the test of such (or all) tickets.

That's not a bad idea either--perhaps I'll play around with that.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Why does the patchbot not test tickets that are determined to be "spkg" updates?

[Erik Bray]

Hi Thierry, thanks for clarifying on this--

On Fri, Nov 10, 2017 at 1:04 PM, Thierry
 wrote:
> Hi,
>
> On Fri, Nov 10, 2017 at 12:35:51PM +0100, Erik Bray wrote:
>> It seems to me those should be among the most important, if not *the*
>> most important tickets to farm out to patchbots across multiple
>> platforms.  If it made sense to I would set my Windows patchbot to
>> prioritize these among all others.
>>
>> New versions of packages are far more likely to break across
>> platform-related issues than, say, updates to non-platform specific
>> Python and Cython code.
>>
>> What is the reason for this, and is there anything I can do to improve
>> this situation?
>
> IIRC, this was for security reasons. I am +1 to allow those tickets to be
> patchbot tested, as an option (not by default).

Okay, this *sort of* makes sense.  I write "sort of" because it's not
immediately clear what the "security" concern is compared to any other
ticket.  Any change to Sage can contain arbitrary code.  While it's
true that changes to third-party packages are less immediately
transparent than patches to Sage's own codebase, at the end of the day
the risk is the same--anyone who can post a ticket to Sage's Trac and
who is already "trusted" by the patchbots (and the default is to only
run changes by "trusted" authors as it is) can make a risky change.

If there were a security risk to a third-party package this doesn't
offer any protection to those patchbots in the long term because as
soon as the package update is merged those patchbots will start
building with the updated package.

> I personally run my patchbot within a VM (actually i have to since i have
> to emulate 32-bit architecture for Sage Debian Live), so i will volonteer
> to test such tickets. I have an automatic way to bootstrap such patchbot
> VM (more-or-less every supported versions of Debian and Ubuntu, both 32
> and 64 bits, if there is a strong need, i could work on supporting more
> distros and architectures), so i am thinking on providing ready-to-run
> patchbots for users that do not want to take risks for their computers,
> nor loose time in setting such things up.

Right--anyone who is running a patchbot on either a personal machine,
or at least not in a VM, is accepting the risk to run arbitrary code
on it (which is a risk they should not accept IMO, but there's only so
much we can do to protect them from that).

As for testing on more distros I do have a plan for that which I hope
to enact soon.  I have a patchbot running with the Ubuntu-based Docker
image that has been working well for some time.  There have been a few
tiny issues specific to running the tests in Docker, but in general
this is no different from testing directly on that distro.  So my plan
is to make more Sage docker images for other distros (plain Debian,
CentOS, Arch, Gentoo, and Alpine are among my top priorities but I'd
welcome input on that).  Then I can run patchbots with all of them.

> Note however that it is not clear what to do with such tickets: by default
> a patchbot runs the tests only with respect to the packages installed by
> its owner. In this case, if the owner did not install the corresponding
> package (which will always be the case if the ticket is about a new
> package), the patchbot will report a possibly wrong false positive.

I don't understand the issue here--if a package is a dependency of
Sage then it will be built, right?  This only seems to apply to
optional packages.

> But, if we want to add an option to let the patchbot install a new package
> proposed by some ticket, after testing that ticket, the patchbot will be
> in a different state than before to test other tickets, in this situation,
> the patchbot will report possibly wrong false negative.

Ah, well that's where my improved package uninstallation system comes
in:  https://trac.sagemath.org/ticket/22510

This actually works very well in my testing so far, but getting the
functionality merged is taking some time as there are some difficult
prerequisites (e.g. https://trac.sagemath.org/ticket/22509).

As a temporary alternative, I suppose that if a *new* package is
installed I suppose the patchbot can run `make distclean` after that
build.  That will slow things down considerably for the next build
but...oh well?

> So, at the end, we have an issue with our packaging system: there is no
> systematic way to uninstall a package.

Well, there is now, if it ever gets merged... :)

Thanks,
Erik

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Why does the patchbot not test tickets that are determined to be "spkg" updates?

[Thierry]

On Fri, Nov 10, 2017 at 01:04:36PM +0100, Thierry wrote:
[...]
> But, if we want to add an option to let the patchbot install a new package
> proposed by some ticket, after testing that ticket, the patchbot will be
> in a different state than before to test other tickets, in this situation,
> the patchbot will report possibly wrong false negative.

A workaround for that (at least on decent OSes), would be to have a
unionfs mechanism that adds a disposable layer mounted on $SAGE_ROOT/local
and $SAGE_ROOT/src/build during the test of such (or all) tickets.

Ciao,
Thierry

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Why does the patchbot not test tickets that are determined to be "spkg" updates?

[Thierry]

Hi,

On Fri, Nov 10, 2017 at 12:35:51PM +0100, Erik Bray wrote:
> It seems to me those should be among the most important, if not *the*
> most important tickets to farm out to patchbots across multiple
> platforms.  If it made sense to I would set my Windows patchbot to
> prioritize these among all others.
> 
> New versions of packages are far more likely to break across
> platform-related issues than, say, updates to non-platform specific
> Python and Cython code.
> 
> What is the reason for this, and is there anything I can do to improve
> this situation?

IIRC, this was for security reasons. I am +1 to allow those tickets to be
patchbot tested, as an option (not by default).

I personally run my patchbot within a VM (actually i have to since i have
to emulate 32-bit architecture for Sage Debian Live), so i will volonteer
to test such tickets. I have an automatic way to bootstrap such patchbot
VM (more-or-less every supported versions of Debian and Ubuntu, both 32
and 64 bits, if there is a strong need, i could work on supporting more
distros and architectures), so i am thinking on providing ready-to-run
patchbots for users that do not want to take risks for their computers,
nor loose time in setting such things up.

Note however that it is not clear what to do with such tickets: by default
a patchbot runs the tests only with respect to the packages installed by
its owner. In this case, if the owner did not install the corresponding
package (which will always be the case if the ticket is about a new
package), the patchbot will report a possibly wrong false positive.

But, if we want to add an option to let the patchbot install a new package
proposed by some ticket, after testing that ticket, the patchbot will be
in a different state than before to test other tickets, in this situation,
the patchbot will report possibly wrong false negative.

So, at the end, we have an issue with our packaging system: there is no
systematic way to uninstall a package.

Ciao,
Thierry



> Thanks,
> Erik
> 
> -- 
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Why does the patchbot not test tickets that are determined to be "spkg" updates?

[Erik Bray]

It seems to me those should be among the most important, if not *the*
most important tickets to farm out to patchbots across multiple
platforms.  If it made sense to I would set my Windows patchbot to
prioritize these among all others.

New versions of packages are far more likely to break across
platform-related issues than, say, updates to non-platform specific
Python and Cython code.

What is the reason for this, and is there anything I can do to improve
this situation?

Thanks,
Erik

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Development tasks

[Vincent Delecroix]

Dear Andy,

You could also help improving the patchbot (written in pure Python)

https://github.com/sagemath/sage-patchbot

For example:

* fixing some false positive
* better support for testing of optional packages
* logs should not go in SAGE_ROOT/logs/patchbot/

Would you be interested?

Vincent

On 09/11/2017 14:40, Andy Howell wrote:

I've been using Sage on and off for a number of years, and am currently
using it while re-learning the calculus I took 35+ years ago. I'm
definitely the oldest in my class this time around!

I'm running the current dev version under Ubuntu 17.04. I have to move to
another laptop temporarily. The build on Ubuntu 17.10 is failing on
openBlas. I'll make another post about that issue.

I'm interested in helping out on Sage in some small way. I've had a look
through the trac list for beginners, but didn't see anything that was an
obvious fit for my skills.

I'm a c++ developer in my day job. I have done some python development, and
ran a buildbot setup for awhile. I don't have the mathematical ability to
take on core issues. Something involving basic python, unit testing,
documentation etc would be a good fit.

I saw that there is work on supporting python 3. Is there more that needs
doing on that? Maybe more doctests? Documentation?

I'm looking for suggestions on where I can get started.

Thanks,

Andy


--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] p-adic factorization/root finding bug.

[Simon Brandhorst]

{{{
sage: f=x^22 + 9*x^21 + 16*x^20 - 92*x^19 - 408*x^18 - 144*x^17 + 2080*x^16 
+ 4096*x^15 + 128*x^14 - 8192*x^13 - 12800*x^12 - 18432*x^11 - 51200*x^10 - 
131072*x^9 + 8192*x^8 + 1048576*x^7 + 2129920*x^6 - 589824*
: x^5 - 6684672*x^4 - 6029312*x^3 + 4194304*x^2 + 9437184*x + 4194304
: 
sage: f.factor()
(x - 2)^6 * (x + 2)^8 * (x^8 + 5*x^7 + 16*x^6 + 40*x^5 + 88*x^4 + 160*x^3 + 
256*x^2 + 320*x + 256)
sage: g=f.change_ring(Qp(2,200))
sage: g.roots()

[(1 + 2 + 2^3 + 2^4 + 2^5 + 2^7 + 2^8 + 2^10 + 2^11 + 2^12 + 2^15 + 2^16 + 
2^19 + 2^20 + 2^22 + 2^28 + 2^31 + 2^32 + 2^38 + 2^39 + 2^40 + 2^41 + 2^43 
+ 2^44 + 2^46 + 2^47 + 2^50 + 2^53 + 2^54 + 2^56 + 2^57 + 2^59 + 2^60 + 
2^61 + 2^68 + 2^71 + 2^74 + 2^75 + 2^76 + 2^77 + 2^84 + 2^86 + 2^89 + 2^90 
+ 2^94 + 2^95 + 2^97 + 2^100 + 2^106 + 2^107 + 2^110 + 2^112 + 2^113 + 
2^118 + 2^119 + 2^124 + 2^126 + 2^127 + 2^128 + 2^132 + 2^135 + 2^141 + 
2^143 + 2^145 + 2^146 + 2^147 + 2^148 + 2^149 + 2^150 + 2^151 + 2^152 + 
2^155 + 2^160 + 2^162 + 2^165 + 2^166 + 2^168 + 2^170 + 2^171 + 2^173 + 
2^174 + 2^176 + 2^177 + 2^180 + 2^181 + 2^183 + 2^184 + 2^185 + 2^187 + 
2^189 + 2^190 + 2^191 + 2^192 + 2^193 + 2^194 + 2^195 + 2^196 + 2^197 + 
2^198 + O(2^200),
  1),
 (2^2 + 2^3 + 2^6 + 2^7 + 2^8 + 2^10 + 2^11 + 2^12 + 2^13 + 2^14 + 2^17 + 
2^18 + 2^20 + 2^23 + 2^24 + 2^28 + 2^29 + 2^33 + 2^34 + 2^36 + 2^39 + 2^40 
+ 2^42 + 2^44 + 2^45 + 2^47 + 2^54 + 2^55 + 2^56 + 2^58 + 2^59 + 2^61 + 
2^63 + 2^69 + 2^70 + 2^71 + 2^78 + 2^81 + 2^82 + 2^84 + 2^87 + 2^88 + 2^89 
+ 2^90 + 2^91 + 2^93 + 2^95 + 2^99 + 2^100 + 2^101 + 2^102 + 2^103 + 2^104 
+ 2^108 + 2^110 + 2^113 + 2^115 + 2^116 + 2^117 + 2^118 + 2^121 + 2^122 + 
2^123 + 2^124 + 2^126 + 2^128 + 2^130 + 2^131 + 2^133 + 2^135 + 2^137 + 
2^139 + 2^140 + 2^141 + 2^142 + 2^144 + 2^145 + 2^146 + 2^148 + 2^151 + 
2^152 + 2^157 + 2^158 + 2^159 + 2^163 + 2^165 + 2^166 + 2^169 + 2^170 + 
2^171 + 2^174 + 2^175 + 2^176 + 2^177 + 2^179 + 2^181 + 2^182 + 2^184 + 
2^188 + 2^192 + 2^193 + 2^194 + 2^195 + 2^196 + 2^198 + O(2^200),
  1)]


}}}


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.