[sage-devel] Re: New contributor experience

[Jerry James]

On Saturday, July 6, 2019 at 4:54:45 AM UTC-6, Samuel Lelievre wrote:
>
> Dear Jerry,
>
> thanks for reporting. We should make the change you suggest.
>
> At some point we had a bot that transformed pull requests
> on the SageMath repo at *GitHub* into Sage Trac tickets but
> the code for this bot was lost at some point.
>
> Instead we now have a bot that transforms merge requests
> on the SageMath repo at *GitLab* into Sage Trac tickets:
>
> https://gitlab.com/sagemath/sage
>
> The process is the same as with GitHub, the only difference
> being that GitLab calls "merge request" what GitHub calls
> "pull request". Fork the repository, make changes on your fork,
> create a merge request.
>
> We should update the documentation to reflect that.
>
> Samuel
>

Okay, that is good to know.  At this point, I am already set up to use git 
trac, so I will continue down that path.  Thank you for the reply!  Regards,
-- 
Jerry James 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8bd62f36-1b1b-43dc-a591-605ce15770a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: constant function which can be evaluated for any value but cannot be integrated numerically

[Emmanuel Charpentier]

This seems to be a follow-up to this 

 ask.sahemath.org 
question.


   1. As already pointed out by Serge Lelièvre, this anomaly doesn't 
   happent in a Python3-based Sage. Possibly, the behaviour of floats raised 
   to a negative fractional power are different ?
   2. I took the liberty of pointing future  ask.sagemath readers to this 
   sage-devel thread for future reference.


HTH,

Le vendredi 5 juillet 2019 22:58:12 UTC+2, Piotr Sniady a écrit :
>
> Dear Developers,
>
> the code below produces a function which for any real u<3 gives as value 
> \pi/3.
> One can check that for any given number Sage has no problems to evaluate 
> this function
> and that it gives the right value.
>
> For strange reason I cannot integrate this function numerically.
> Also, I cannot plot this function.
>
> Magically, while for any given value Sage has no problems to give a 
> complex root of a negative number,
> for numerical integration the behavior of the root changes.
>
> Any help would be appreciated.
>
> Yours,
>
> Piotr
>
>
>
> def F(u):
> return arg( (-3 + u )^(1/3) ).n()
>
> numerical_integral(F,1,2)
>
>
>
>
> Error message:
>
> negative number cannot be raised to a fractional power
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/25731a37-ae73-470b-b943-6da6f1d9ef4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: patchbot security

['Jonathan Kliem' via sage-devel]

Thanks, I have to see what I can do about it (I went through all the 
tickets I tested and it looks things are fine).

Am Samstag, 6. Juli 2019 14:50:51 UTC+2 schrieb Volker Braun:
>
> The patchbot configuration has some options for trusting specific user 
> accounts.
>
> Having said that, you are correct in that it executes code submitted by 
> strangers over the internet. At the very least make a separate user account 
> for running the patchbot. You might want to add an additional container / 
> vm layer.
>
 
Could you (or someone else) add this info to 
https://wiki.sagemath.org/patchbot.


>
>
> On Saturday, July 6, 2019 at 4:20:09 AM UTC-4, Jonathan Kliem wrote:
>>
>> Hi,
>>
>> I'm wondering what safety measures are taken for distributing code to the 
>> patchbot clients.
>>
>> E.g. if I where to register a new github account and create a ticket that 
>> uploads all files from the user to a server of my choice (maybe via a 
>> malicous doctest), is that ticket still going to be distributed to patchbot 
>> clients?
>>
>> I guess the underlying question is, what security measures are 
>> recommended before running a patchbot. On 
>> https://wiki.sagemath.org/patchbot I cannot find anything.
>>
>> Jonathan
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d67196d2-6b2f-450c-aabc-54266311556c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: patchbot security

[Volker Braun]

The patchbot configuration has some options for trusting specific user 
accounts.

Having said that, you are correct in that it executes code submitted by 
strangers over the internet. At the very least make a separate user account 
for running the patchbot. You might want to add an additional container / 
vm layer.



On Saturday, July 6, 2019 at 4:20:09 AM UTC-4, Jonathan Kliem wrote:
>
> Hi,
>
> I'm wondering what safety measures are taken for distributing code to the 
> patchbot clients.
>
> E.g. if I where to register a new github account and create a ticket that 
> uploads all files from the user to a server of my choice (maybe via a 
> malicous doctest), is that ticket still going to be distributed to patchbot 
> clients?
>
> I guess the underlying question is, what security measures are recommended 
> before running a patchbot. On https://wiki.sagemath.org/patchbot I cannot 
> find anything.
>
> Jonathan
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/51233fce-98dc-46b9-b643-5e912a994bf0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: New contributor experience

[Samuel Lelievre]

Le samedi 6 juillet 2019 00:56:40 UTC+2, Jerry James a écrit :
>
> Greetings,
>
> I help out with maintaining the sagemath package and many of its 
> dependencies for the Fedora Linux distribution.  While performing 
> maintenance activities, I have produced a handful of patches that I would 
> like to submit to you.
>
> I found http://www.sagemath.org/development.html.  The 2nd and 3rd 
> bullets in the list ("SageMath FAQ" and "How to contribute to SageMath", 
> respectively) go to the same place.  That's because the 3rd bullet points 
> to the first entry on the page pointed to by the 2nd bullet.  I found this 
> distinction more confusing than helpful.  (My reaction on clicking the 3rd 
> link was, "Wait, I just read this page!  Did I accidentally click on the 
> 2nd bullet again?".  Click on the back button.  Click on the 3rd bullet 
> again.  No, same place.  Let's look at the URLs.  O.)  I recommend you 
> eliminate one of the two.
>
> I started working my way through the Sage Developer's Guide.  Near the 
> top, under the bullet named "Git (revision control)", is a link to 
> http://doc.sagemath.org/html/en/developer/walk_through.html#chapter-walkthrough
>  
> named "Here is an overview of our development flow".  The third paragraph 
> on the linked page says, "You can alternatively fork and create a pull 
> request at github which will automatically fetch your code and open a 
> ticket on our trac server."  Oh, that's great!  So I went to 
> https://github.com/sagemath/sage, where at the top it clearly says, 
> "Mirror of the Sage source tree -- please do not submit PRs here -- 
> everything must be submitted via https://trac.sagemath.org/;.  Wait, that 
> contradicts what I just read in the walkthrough, doesn't it?  Did I fail to 
> understand something?
>
> I ignored the part about pull requests and worked my way through the rest 
> of the guide.  I filed trivial ticket 28124 just to make sure I understand 
> the workflow before moving on.  It would be great if the bit about pull 
> requests could be clarified, though.  If that really works, that would make 
> submitting patches much simpler for me.
>
> Thanks for making such a great piece of software.
> -- Jerry James
>

Dear Jerry,

thanks for reporting. We should make the change you suggest.

At some point we had a bot that transformed pull requests
on the SageMath repo at *GitHub* into Sage Trac tickets but
the code for this bot was lost at some point.

Instead we now have a bot that transforms merge requests
on the SageMath repo at *GitLab* into Sage Trac tickets:

https://gitlab.com/sagemath/sage

The process is the same as with GitHub, the only difference
being that GitLab calls "merge request" what GitHub calls
"pull request". Fork the repository, make changes on your fork,
create a merge request.

We should update the documentation to reflect that.

Samuel

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3fa625d1-a855-4bb4-b222-9840311a46ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] patchbot security

['Jonathan Kliem' via sage-devel]

Hi,

I'm wondering what safety measures are taken for distributing code to the 
patchbot clients.

E.g. if I where to register a new github account and create a ticket that 
uploads all files from the user to a server of my choice (maybe via a 
malicous doctest), is that ticket still going to be distributed to patchbot 
clients?

I guess the underlying question is, what security measures are recommended 
before running a patchbot. On https://wiki.sagemath.org/patchbot I cannot 
find anything.

Jonathan

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/928b6679-16ec-4f85-b737-2a8c10c19155%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: patchbot server down

['Jonathan Kliem' via sage-devel]

In my case it crashed (might have been because I tried to start it during 
downtime).

By looking at https://patchbot.sagemath.org/machines I'm having the 
impression that I'm not the only one, where this happened.

Am Samstag, 6. Juli 2019 07:46:41 UTC+2 schrieb Frédéric Chapoton:
>
> No. No need to restart any patchbot client.
>
> F
>
> Le samedi 6 juillet 2019 07:17:59 UTC+2, Jonathan Kliem a écrit :
>>
>> Great,
>>
>> so I guess all patchbots have to be restarted (if not already done so).
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d246455b-9cb3-4466-a75a-3b17c0bf73e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.