[sage-devel] (Re-)building an inclusive SageMath community. II: Recognizing and fighting abuse, bullying, disrespect

2024-04-12 Thread Matthias Koeppe
Trigger Warning: In this post, I will discuss topics that can make some people uncomfortable; in particular readers who have themselves been the target of abuse, bullying, and disrespect in the past. (I apologize if I have omitted this Trigger Warning in previous posts that touched these topics

Re: [sage-devel] Urgent: Please vote on these "disputed" PRs

2024-04-12 Thread jplab
Dear all, The Code of Conduct Committee considered the issue and found no need for David to recuse himself as requested. We would like to use this opportunity to clarify that messages sent by any of us and signed as “The Code of Conduct Committee” have been approved by the entire committee.

Re: [sage-devel] Urgent: Please vote on these "disputed" PRs

2024-04-12 Thread Matthias Koeppe
I have asked David Roe to recuse himself from any further discussions/actions involving me in the CoCC. The persistent refusal to make a distinction between *abusive conduct* and *calling out abuse* has caused too much damage already. Matthias On Wednesday, April 10, 2024 at 9:28:40 PM UTC-7 D

Re: [sage-devel] SEGV caused by CTL-C in C/C++ code probably related to signals

2024-04-12 Thread julian...@fsfe.org
Thanks a lot for this really quick fix Dima. I gave it positive review already. On Friday, April 12, 2024 at 4:27:31 PM UTC+3 Georgi Guninski wrote: My results differ. If you want more systematic approach for QA and security (the recent paranoia induced by the xz backdoor) you will need moderat

Re: [sage-devel] SEGV caused by CTL-C in C/C++ code probably related to signals

2024-04-12 Thread Georgi Guninski
My results differ. If you want more systematic approach for QA and security (the recent paranoia induced by the xz backdoor) you will need moderate budget possibly with zero trust to me. Have a nice weekend. On Fri, Apr 12, 2024 at 3:52 PM Dima Pasechnik wrote: > > > > On 12 April 2024 12:42:39

Re: [sage-devel] SEGV caused by CTL-C in C/C++ code probably related to signals

2024-04-12 Thread Dima Pasechnik
On 12 April 2024 12:42:39 CEST, Georgi Guninski wrote: >On Fri, Apr 12, 2024 at 11:35 AM Dima Pasechnik wrote: >> >> This should be fixed by https://github.com/sagemath/sage/pull/37792 >> please review >> > >I suspect reproducing is hard, since it depends on the time of pressing CTL-C. Well,

Re: [sage-devel] SEGV caused by CTL-C in C/C++ code probably related to signals

2024-04-12 Thread Georgi Guninski
On Fri, Apr 12, 2024 at 11:35 AM Dima Pasechnik wrote: > > This should be fixed by https://github.com/sagemath/sage/pull/37792 > please review > I suspect reproducing is hard, since it depends on the time of pressing CTL-C. Also, lack a crash may be silent memory corruption. It is weird that the

Re: [sage-devel] SEGV caused by CTL-C in C/C++ code probably related to signals

2024-04-12 Thread Dima Pasechnik
This should be fixed by https://github.com/sagemath/sage/pull/37792 please review On Thursday, April 11, 2024 at 10:19:31 PM UTC+1 dim...@gmail.com wrote: > On Thu, Apr 11, 2024 at 03:30:34PM +0300, Georgi Guninski wrote: > > Are the non-crashing codepaths in consistent state? > > SEGV is in gene