[sage-devel] Re: Proposal: ci codecov/patch reports but not fail

On Saturday, October 5, 2024 at 6:38:20 AM UTC-7 Kwankyu Lee wrote: But I don't know how big a problem the codecov issue is ... We want to regard the check failure as there is a problem with the PR that the author should resolve. Currently the codecov failure triggers the check failur

[sage-devel] Re: Build failure for cypari on Apple Silicon, Sequoia 15.0.1

When I have time, I will verify that a complete Sage build succeeds. On Friday, October 4, 2024 at 2:46:15 PM UTC-7 John H Palmieri wrote: > I upgraded one machine to Sequoia 15.0.1 today, and now cypari fails to > build. This is an Apple Silicon laptop with many homebrew packages > i

Re: [sage-devel] trouble installing sage

On Thursday, September 26, 2024 at 3:27:50 PM UTC-7 dim...@gmail.com wrote: On Thu, Sep 26, 2024 at 10:56 PM John H Palmieri wrote: > > Before deleting anything, you could try expunging all mention of /usr/local from your PATH and other variables wherever they're set (.profile

Re: [sage-devel] trouble installing sage

pkg-config > > >>>>>>> > > >>>>>>> On Wed, Sep 25, 2024 at 4:45 PM Anne Schilling > > >>>>>>> wrote: > > >>>>>>>> Hi Dima and Kwankyu, > > >>>>>>>> > > >>>>>>

Re: [sage-devel] trouble installing sage

> /Users/anne/sage/sage/build/pkgs/sagemath_mcqd/src/pyproject.toml > >>>> >> > ./bootstrap: installing > /Users/anne/sage/sage/build/pkgs/sagemath_mcqd/src/requirements.txt > >>>> >> > ./bootstrap: installing > /Users/anne/sage/sage/bui

Re: [sage-devel] trouble installing sage

On Tuesday, September 24, 2024 at 3:19:07 PM UTC-7 dim...@gmail.com wrote: >From the log: ./configure --enable-system-site-packagesls (SIC!) ## Checking whether SageMath should install SPKG scipy... ## ## -- ## configure:90867: checking

Re: [sage-devel] trouble installing sage

For what it's worth, I just upgraded a machine to OS X 15.0, Xcode 16.0, and as many homebrew packages as Sage requested, and Sage built just fine. I'm seeing some doctest errors, presumably because of the new Xcode: lots of warning messages saying something like "warning: ld_classic is deprec

Re: Allow logical failover slots to wait on synchronous replication

Hi, On Fri, Sep 20, 2024 at 2:44 AM shveta malik wrote: > > > > > > > The difference is that the purpose of 'synchronized_standby_slots' is > > to mention slot names for which the user expects logical walsenders to > > wait before sending the logical changes to subscribers. OTOH, > > 'synchronous

Re: Allow logical failover slots to wait on synchronous replication

Hi, On Mon, Sep 16, 2024 at 2:25 AM shveta malik wrote: > > > > > > If we don't do something similar, then aren't there chances that we > > > keep on waiting on the wrong lsn[mode] for the case when mode = > > > SYNC_REP_WAIT_APPLY while sync-rep-wait infrastructure is updating > > > different m

Re: Allow logical failover slots to wait on synchronous replication

Hi Shveta, On Sun, Sep 8, 2024 at 11:16 PM shveta malik wrote: > > I was trying to have a look at the patch again, it doesn't apply on > the head, needs rebase. > Rebased with the latest changes. > Regarding 'mode = SyncRepWaitMode', FWIW, SyncRepWaitForLSN() also > does in a similar way. It g

[sage-devel] Re: Policy discussion about blocking others on Github

Just to clarify: my response was my own, not that of the Code of Conduct Committee. On Sunday, September 8, 2024 at 11:03:11 PM UTC-7 Kwankyu Lee wrote: > Thank John for the response. > > I have other questions in > https://groups.google.com/g/sage-devel/c/cLnRyofH0lw/m/S__tbpV1AgAJ. They > a

[sage-devel] Re: Policy discussion about blocking others on Github

(a) Your point about "SageMath" being redundant is a good one. (b) Some people do not use either pronoun "him" or "her", and so "them" covers more options. (The use of "they/them" as a generic singular pronoun is common, at least in US academic settings.) (c) I think that the sanctions should de

Re: [sage-release] Re: Sage 10.5.beta3 released

o make the test more generic - after all it tests an error > message! > > Dima > > > On 5 September 2024 19:04:27 BST, John H Palmieri > wrote: > >> I think this is a new failure. Could it be due to an upgraded system >> package? >> >> sage -t --r

[sage-release] Re: Sage 10.5.beta3 released

I think this is a new failure. Could it be due to an upgraded system package? sage -t --random-seed=232711236884461766258917891173593419501 src/sage/graphs/generators/families.py ** File "src/sage/graphs/generators/families.py",

Re: Switching XLog source from archive to streaming when primary available

Hi, On Thu, Aug 29, 2024 at 6:32 AM Bharath Rupireddy wrote: > In synchronous replication setup, until standby finishes fetching WAL > from the archive, the commits on the primary have to wait which can > increase the query latency. If the standby can connect to the primary > as soon as the broke

Re: Allow logical failover slots to wait on synchronous replication

Hi Shveta, Thanks for reviewing it so quickly. On Thu, Aug 29, 2024 at 2:35 AM shveta malik wrote: > > Thanks for the patch. Few comments and queries: > > 1) > + static XLogRecPtr lsn[NUM_SYNC_REP_WAIT_MODE]; > > We shall name it as 'lsns' as there are multiple. > This follows the same na

Re: Allow logical failover slots to wait on synchronous replication

Hi Amit, On Mon, Aug 26, 2024 at 11:00 PM Amit Kapila wrote: > I wanted a simple test where in the first case you use > synchronous_standby_names = 'ANY 3 (A,B,C,D,E)' and in the second case > use standby_slot_names = A_slot, B_slot, C_slot, D_slot, E_slot. You > can try some variations of it as

Re: Allow logical failover slots to wait on synchronous replication

Hi Bertrand, On Sun, Jul 28, 2024 at 10:00 PM Bertrand Drouvot wrote: > Yeah, at the same place as the static lsn[] declaration, something like: > > static XLogRecPtr lsn[NUM_SYNC_REP_WAIT_MODE]; /* cached LSNs */ > > but that may just be a matter of taste. > I've updated the patch to ref

Re: Allow logical failover slots to wait on synchronous replication

Hi Shveta, Amit, > > > > ... We should try to > > > > find out if there is a performance benefit with the use of > > > > synchronous_standby_names in the normal configurations like the one > > > > you used in the above tests to prove the value of this patch. I don't expect there to be a performan

Re: Allow logical failover slots to wait on synchronous replication

Hi Shveta, On Sun, Jul 21, 2024 at 8:42 PM shveta malik wrote: > > Ah that's a gap. Let me add some logging/warning in a similar fashion. > > Although I think I'd have the warning be relatively generic (e.g. > > changes are blocked because > > they're not synchronously committed) > > > > okay, s

Re: Switching XLog source from archive to streaming when primary available

Hi, I took a brief look at the patch. For a motivation aspect I can see this being useful synchronous_replicas if you have commit set to flush mode. So +1 on feature, easier configurability, although thinking about it more you could probably have the restore script be smarter and provide non-zero

Re: [sage-devel] Re: Policy discussion about hiding GitHub comments

r discussion rather than a vote. >> David >> >> On Thu, Aug 22, 2024 at 2:32 PM Matthias Koeppe >> wrote: >> >>> On Thursday, August 22, 2024 at 11:08:48 AM UTC-7 John H Palmieri wrote: >>> >>> This message comes from the Code of Conduct

[sage-devel] Policy discussion about editing GitHub comments and PR/issue descriptions

This message comes from the Code of Conduct Committee, in response to a question from Kwankyu (labeled A4 in his message) about the authority to modify a comment by someone else (including PR and issue descriptions).

[sage-devel] Policy discussion about hiding GitHub comments

This message comes from the Code of Conduct Committee, in response to a question from Kwankyu (labeled A1 in his message) about the authority to mark a comment as off topic, and more generally about hiding comments. Propo

[sage-devel] Re: Proposal: Demote jupyter-jsmol and tachyon to optional

On Tuesday, August 20, 2024 at 6:45:41 AM UTC-7 Kwankyu Lee wrote: On Tuesday, August 20, 2024 at 7:07:54 PM UTC+9 Eric Gourgoulhon wrote: There are tons of png files in the "3d Graphics" section of the documentation: https://doc.sagemath.org/html/en/reference/plot3d/sage/plot/plot3d/plot3d.

[sage-devel] Re: message marked as off topic

Hi Kwankyu, (This is a response from the Code of Conduct Committee.) Thank you for raising these issues. Some are addressed below, and we will also create separate threads (for discussion of policy proposals) to deal with some of the others. On Wednesday, August 14, 2024 at 3:54:30 PM UTC-7 Kw

[sage-release] Re: Sage 10.5.beta2 released

I think this failure is due to https://github.com/sagemath/sage/pull/38492 On Tuesday, August 13, 2024 at 3:50:06 PM UTC-7 John H Palmieri wrote: > This looks like a new failure on OS X 14.5: > > sage -t --long --warn-long 24.7 > --random-seed=330717456732602079039915918344955119792

[sage-devel] Re: message marked as off topic

In my opinion, the decision to hide a comment should not be made by a single person. I might even suggest that the authority to make such a decision should lie solely with the Sage Code of Conduct Committee. (I am a member of that committee, but I am expressing my own views here, not those of t

[sage-release] Re: Sage 10.5.beta2 released

This looks like a new failure on OS X 14.5: sage -t --long --warn-long 24.7 --random-seed=330717456732602079039915918344955119792 src/sage/modules/free_quadratic_module_integer_symmetric.py ** File "src/sage/modules/free_quadrat

Re: [sage-devel] Re: ssl problem

That means that at least one of bzip2, liblzma, libffi, zlib are being built by Sage. Can you install system versions of these instead? What does the message say at the end of running `./configure`? John On Wednesday, July 31, 2024 at 11:31:08 AM UTC-7 axio...@yahoo.de wrote: > Is this the

Re: Allow logical failover slots to wait on synchronous replication

Hi Bertrand, > 1 === > ... > That's worth additional comments in the code. There's this comment already about caching the value already, not sure if you prefer something more? /* Cache values to reduce contention on lock */ > 2 === > ... > Looks like setting initialized to true is missing once

Re: Allow logical failover slots to wait on synchronous replication

Hi Shveta, Thanks for taking a look at the patch. > > will leave user no option to unlink failover-enabled logical > > subscribers from the wait on synchronous standbys. That's a good point. I'm a bit biased in that I don't think there's a great reason why someone would want to replicate logical

Re: Allow logical failover slots to wait on synchronous replication

Hi Amit, Thanks for taking a look. On Tue, Jun 18, 2024 at 10:34 PM Amit Kapila wrote: > > > The reading indicates when you set 'standby_slot_names_from_syncrep', > the TPS reduces as compared to when it is not set. It would be better > to see the data comparing 'standby_slot_names_from_syncrep

Re: Allow logical failover slots to wait on synchronous replication

Hi, Thanks Bertrand for taking a look at the patch. On Mon, Jun 17, 2024 at 8:19 AM Bertrand Drouvot wrote: > > + int mode = SyncRepWaitMode; > > It's set to SyncRepWaitMode and then never change. Worth to get rid of "mode"? > I took a deeper look at this with GDB and I think it'

Re: [sage-devel] Italicizing inside a literal block

It doesn't sound like you want a literal block, but rather a block quote or similar: a block of text that is parsed but highlighted somehow. Maybe (but this is untested) .. rubric: Theorem include text here Look at https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#di

Re: Addressing SECURITY DEFINER Function Vulnerabilities in PostgreSQL Extensions

Hi Ashutosh, Thanks for clarifying. > not standalone functions created independently I'm wondering why we wouldn't want to extend that functionality so that if users (including superusers) do want to automatically configure search_path when they're creating functions it's available. > The diff

Re: Addressing SECURITY DEFINER Function Vulnerabilities in PostgreSQL Extensions

extension > that does not have the search_path explicitly set in proconfig If that's the "general" issue you're trying to solve, I would wonder why we we wouldn't for instance be extending the functionality to normal CREATE FUNCTION calls (ie, schema qualify based off s

Re: Addressing SECURITY DEFINER Function Vulnerabilities in PostgreSQL Extensions

Hi, > I know about the problem and have seen the original email. I'm sympathetic to the problem of potential privilege escalation when executing functions. At the same time I'm not sure if there's that much of a difference between 'CREATE EXTENSION' vs superusers copying a series of 'CREATE FUNC

Allow logical failover slots to wait on synchronous replication

Hi hackers, Building on bf279ddd1c, this patch introduces a GUC 'standby_slot_names_from_syncrep' which allows logical failover slots to wait for changes to have been synchronously replicated before sending the decoded changes to logical subscribers. The existing 'standby_slot_names' isn't great

[sage-release] Re: Sage 10.4.beta8 released

This issue with "convert" has already been reported, with a proposed fix, at https://github.com/sagemath/sage/pull/38135. On Wednesday, June 5, 2024 at 6:32:15 PM UTC-7 John H Palmieri wrote: > I don't think I've seen this failure before: > >

[sage-release] Re: Sage 10.4.beta8 released

I don't think I've seen this failure before: sage -t --long --random-seed=214696321465302976857414484526305325295 src/sage/plot/plot3d/tachyon.py ** File "src/sage/plot/plot3d/tachyon.py", line 126, in sage.plot.plot3d.tachyon F

[sage-release] Re: Sage 10.4.beta5 released

After running `make configure`, the git repository is not clean: % git status On branch develop Your branch is up to date with 'upstream/develop'. Untracked files: (use "git add ..." to include in what will be committed) pkgs/sagemath-categories/requirements-editable.txt pkgs/sagemath-environm

Re: [sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

er out the warnings when doctesting. -- John On Thursday, April 25, 2024 at 1:19:50 PM UTC-7 John H Palmieri wrote: > Take a look at the discussion at > https://github.com/sagemath/sage/pull/36337, in particular > https://github.com/sagemath/sage/pull/36337#issuecomment-1741293729. I &g

Re: [sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

if the "duplicate libraries" warnings are caused by duplicate > rpath entries in the mach files. I will try to test that hypothesis. > > Do you have any idea what could cause those duplicate rpaths? Are there > multiple -rpath options being passed to the compiler? > >

[sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

Hi Marc, I just tried building Sage without `-ld-classic`. It builds, but I get warnings about "ignoring duplicate libraries", and those cause doctest failures. The lines could be modified to test whether xcode-select is present and executable first, or since Sage now does indeed build without

Re: [sage-devel] Re: Proposal (redo): Make python_build (and its dependency pyproject_hooks) a standard package

+1 to the inclusion of the package, in case anyone views the voting as still open. François, thank you for letting us know about how the ongoing disputes are affecting you. I feel your pain. Regards, John On Monday, April 15, 2024 at 2:01:43 PM UTC-7 François Bissey wrote: > > > On 16/04/2

Re: [sage-devel] Mysterious .sage behavior

I searched for "ipython-5.0.0" in the source and found this: if [ -z "$IPYTHONDIR" ]; then # We hardcode a version number in the directory name. The idea is # that we keep using the same version number as long as that is # possible. Only when some future IPython version really requires

[sage-release] Re: Sage 10.4.beta0 released

And on two OS X Apple Silicon machines running Sonoma 14.4.1, new Xcode command line tools, sagelib fails to build, as reported here: https://groups.google.com/g/sage-support/c/05DARjR8PFI/m/ZqCuYjhIAAAJ On Tuesday, March 26, 2024 at 5:20:02 PM UTC-7 John H Palmieri wrote: > OS X In

Re: [sage-support] Errors building Sage 10.3 in Sonoma 14.3.1

I'm having the same problem (I think) with Sage 10.4.beta0 on two different Apple Silicon machines. On Wednesday, March 27, 2024 at 9:58:10 AM UTC-7 Dima Pasechnik wrote: > I've cut out the interesting part of the log. > It's a linker error (IMHO the linking should be done with C++, not > with C

[sage-release] Re: Sage 10.4.beta0 released

OS X Intel machine, documentation fails to build with errors like OSError: [Errno 24] Too many open files: '/var/folders/z6/yjw_7s357yx3_mhh81__lplcgn/T/tmpu490zz15' I just built 10.3.rc4 on the same machine and it succeeded. On Monday, March 25, 2024 at 5:13:42 PM UTC-7 Volker Braun w

[sage-devel] Vote: changes to Sage's Code of Conduct

Dear Sage community, As announced at https://groups.google.com/g/sage-devel/c/Xf6dbPLmKPY/m/p88auKlBAwAJ, I propose some changes to the Code of Conduct. Those changes have been discussed and modified based on feedback from several developers: visit https://github.com/sagemath/sage/pull/37501 f

[sage-devel] Re: Vote: Sage Code of Conduct

Dear all, First, in response to Dima's post: yes, it should definitely be Nils Bruin on the ballot. My sincere apologies to Nils that we got his name wrong! If anyone would like to adjust their ballot in light of this, please let us know and we will make any corrections you request. Second, vo

[cctalk] Re: Did something happen to comp.os.vms ?

o new messages there in comp.os.vms since 3/9 until today (3/12) and then I got 23 messages dated 3/10 - 3/12.  I even did a "Get Messages" several time and nothing.  I don't know if it's Thunderbird or E-S. -- John H. Reinhardt

Re: [sage-devel] Google Season of Docs – org application deadline April 2

Dima's suggestion is appealing, and somewhat along those lines, I like the idea changing Sage to use some standard documentation style (https://github.com/sagemath/sage/issues/31044). If the program provides a technical writer, though, those may not be suitable goals. A quick glance at least ye

[sage-devel] Re: Vote: Sage Code of Conduct

Dear all, Voting continues until Thursday. We have been acknowledging each vote as it comes in, so if you think you voted but have not received an acknowledgment, please email sage-conduct at googlegroups.com. Regards, John On Thursday, March 7, 2024 at 10:46:03 AM UTC-8 John H Palmieri

[sage-devel] Re: Vote: Sage Code of Conduct

> On Thursday 7 March 2024 at 19:39:14 UTC+1 John H Palmieri wrote: > >> Martin: it's "sage-conduct" at googlegroups.com. >> >> On Thursday, March 7, 2024 at 10:29:58 AM UTC-8 Martin R wrote: >> >>> For some reason, I cannot see the name of

[sage-devel] Re: Vote: Sage Code of Conduct

Martin: it's "sage-conduct" at googlegroups.com. On Thursday, March 7, 2024 at 10:29:58 AM UTC-8 Martin R wrote: > For some reason, I cannot see the name of the newsgroup I should be > sending my vote to. (I am using the google groups webinterface) > > Martin > On Thursday 7 March 2024 at 19:13

[sage-devel] Re: VOTE: Use "CI Fix" label for merging into continuous integration runs

+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 view this discussion on the web visit https://groups.google.com/d/m

[sage-devel] Re: VOTE: disputed PRs

+1 On Monday, March 4, 2024 at 12:23:39 AM UTC-8 David Roe wrote: > With no further discussion on this thread > , I'm calling a > vote on a new process for resolving disagreements on a PR. > > *Proposal* > It is now allowed to vote on disput

Re: [sage-devel] VOTE: disputed PRs

Dima, I think that if anyone is incapable of posting to a particular PR, they should send email to someone who can post and ask them to record the person's vote, resulting in a comment like "I am posting to record 1 negative vote from X, 2 positive votes from Y and Z". On Monday, March 4, 2024

Re: [sage-devel] Re: Sage's Code of Conduct: proposed changes

There are suggestions along maybe similar lines at https://github.com/sagemath/sage/pull/36844, and I am trying to think of how we might incorporate your suggestions and the other ones. I've had the thought before about other documents (like our department's by-laws) that there should be two se

[sage-release] Re: Sage 10.3.rc0 released

Wednesday, February 28, 2024 at 2:16:42 PM UTC-8 John H Palmieri wrote: > OS X, Apple Silicon, with many homebrew packages, including a recently > upgraded openjpeg (from 2.5.0 to 2.5.1): pillow is failing to build, with > the error message > > src/libImaging/Jpeg2KDecode

[sage-release] Re: Sage 10.3.rc0 released

OS X, Apple Silicon, with many homebrew packages, including a recently upgraded openjpeg (from 2.5.0 to 2.5.1): pillow is failing to build, with the error message src/libImaging/Jpeg2KDecode.c:673:43: error: too few arguments to function call, expected 3, have 2 opj_stream_set_user_data

[sage-devel] Sage's Code of Conduct: proposed changes

Dear colleagues, I am working on some changes to Sage's Code of Conduct, and I am asking for comments. Once the draft has stabilized, then we will hold a vote on sage-devel to approve (or not) the changes. Please visit https://github.com/sagemath/sage/pull/37501 to see the proposal. The curren

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

On 27 February 2024 20:44:50 GMT, John H Palmieri > wrote: > >Sentences like "At the moment you are actively breaking down the precious > >project fabric, all in the name of you having your way" are personal > >attacks. Please stop. > > Blocking on GitHub m

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

MT, Matthias Koeppe > wrote: > >On Tuesday, February 27, 2024 at 10:50:55 AM UTC-8 John H Palmieri wrote: > > > >A pretty safe second choice would be to have "make download" also > download > >the relevant files for pip installation and tell pip wher

[sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

Regarding the proposal to allow standard packages to be pip packages, no one really knows how much people rely on the all-in-one tarball that we currently distribute. No one really knows how often the "make download" option is used for people who just clone the git repo and want to do all of th

Re: [sage-devel] Re: Unload "blocker" label

(and Tobias also proposed in https://github.com/sagemath/sage/issues/37428) On Monday, February 26, 2024 at 5:05:56 PM UTC-8 John H Palmieri wrote: > I think that usage (1) is the correct use of "blocker," and usage (3) is > not. Usage (2) should have a new name, as Vincent p

Re: [sage-devel] Re: Unload "blocker" label

I think that usage (1) is the correct use of "blocker," and usage (3) is not. Usage (2) should have a new name, as Vincent proposes. Failing that, this new use of "blocker" must be documented in https://doc.sagemath.org/html/en/developer/review.html. On Monday, February 26, 2024 at 4:21:58 PM U

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

You're right, plus I was confusing "./bootstrap -d" (which is run by "make configure") with "./bootstrap -D" which forces the download. On Monday, February 19, 2024 at 3:17:11 PM UTC-8 Matthias Koeppe wrote: > On Monday, February 19, 2024 at 3:09:55 PM U

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

nto that directory. > > > an option to ./bootstrap then would be logical > > >> >> Another possible direction: I've been thinking about creating a "./sage >> worktree" command, see https://github.com/sagemath/sage/issues/34744 >> >> >>

[sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

" another time is > overkill as it creates another copy of the .git directory. And there is no > point in having multiple copies of the "upstream" directory, as the > filenames of the tarballs change whenever the contents change. > > On Monday, February 19, 2024 at

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

On Monday, February 19, 2024 at 12:10:49 PM UTC-8 Dima Pasechnik wrote: On Mon, Feb 19, 2024 at 7:42 PM John H Palmieri wrote: This (A and B below) has the advantage of being quite explicit. The original proposal 1) allow standard packages to be pip packages 2) drop the contents of

[sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

This (A and B below) has the advantage of being quite explicit. The original proposal 1) allow standard packages to be pip packages 2) drop the contents of upstream/ from the Sage source tarballs. sounds explicit, but the more the discussion goes on, the more I feel that there are hidden pie

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

What does this (a discussion of how Sage specifies version restrictions) have to do with the proposal? If it's relevant, that was not clear in the original proposal, so please clarify. It sounds like you might be proposing removing version checks on many of the packages Sage uses, or at least t

[Ubuntu-x-swat] [Bug 2051875] [NEW] monitor goes to sleep (power save) mode as soon as the system attempts to display the graphical login screen. Attempting to switch to a character console wakes the

Public bug reported: https://askubuntu.com/questions/1500676/is-there-a-solution- for-22-04-and-kernel-6-5-0-14-or-6-5-0-15-22-04-for-users?noredirect=1 I'm running 22.04 LTS with an Asus NVidia GeForce GT 730. I'm using the Ubuntu provided video driver (Nouveau). Since upgrading my kernel to 6

[Desktop-packages] [Bug 2051875] [NEW] monitor goes to sleep (power save) mode as soon as the system attempts to display the graphical login screen. Attempting to switch to a character console wakes t

Public bug reported: https://askubuntu.com/questions/1500676/is-there-a-solution- for-22-04-and-kernel-6-5-0-14-or-6-5-0-15-22-04-for-users?noredirect=1 I'm running 22.04 LTS with an Asus NVidia GeForce GT 730. I'm using the Ubuntu provided video driver (Nouveau). Since upgrading my kernel to 6

Re: [sage-support] Re: sage 10.3.b2 build problem on OSX 12.7.1

#sha256=e5b2a84881cf1f40eb5b0115e1d3a429765e0f43743b79e871352bb8e0c95952> > from https://www.piwheels.org/project/flit-core/ to > local/var/lib/sage/venv-python3.9/var/lib/sage/wheels. Then compiling sage > works and flit_core-3.9.0 is installed. > > - Heiko > > Davi

[sage-support] Re: sage 10.3.b2 build problem on OSX 12.7.1

In sage-release, Matthias pointed to missing dependencies for editables, fixed in https://github.com/sagemath/sage/pull/36885. Maybe you can just do "make flit_core" (to build the missing dependency) and then "make". On Friday, December 15, 2023 at 10:52:10 AM UTC-8 David Joyner wrote: > Hi: >

[sage-release] Re: Sage 10.3.beta2 released

restore_term_title _restore_term_title() File "/Users/palmieri/Sage/TESTING/sage-10.3.beta2/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/IPython/utils/terminal.py", line 83, in _restore_term_title_xterm assert _xterm_term_title_saved AssertionError Someth

[sage-release] Re: Sage 10.3.beta2 released

/utils/terminal.py", line 83, in _restore_term_title_xterm assert _xterm_term_title_saved AssertionError The same happens if I execute several commands between the alarm and exit(). On Friday, December 15, 2023 at 7:07:53 AM UTC-8 Dima Pasechnik wrote: > On Thursday, December 14,

Re: [sage-release] Sage 10.3.beta2 released

I'm using Venture 13.6.3 on one machine, Sonoma 14.2 on the other, plus a lot of homebrew packages. On Thursday, December 14, 2023 at 1:05:44 PM UTC-8 david@gmail.com wrote: > I don’t see these errors on Apple M1 with macOS 12.7.1. > > Le 14 déc. 2023 à 17:05, John H Pal

[sage-release] Re: Sage 10.3.beta2 released

On OS X (both Intel and Apple Silicon) I'm getting a lot of new failures, many of the form "Killed due to alarm": sage -t --long --random-seed=144845266083009760424007645487960076680 src/sage/libs/flint/nmod_poly_linkage.pxi # Killed due to alarm sage -t --long --random-seed=1448452660830097604

[sage-support] Re: Problems viewing crystals from sage

to add a comment on the ticket? > > Andrew > > > On Wednesday 13 December 2023 at 12:30:03 pm UTC+11 John H Palmieri wrote: > >> Could this be related to https://github.com/sagemath/sage/pull/36529? >> >> >> On Tuesday, December 12, 2023 at 3:50:55 PM UTC-8 Andrew

[sage-support] Re: Problems viewing crystals from sage

Could this be related to https://github.com/sagemath/sage/pull/36529? On Tuesday, December 12, 2023 at 3:50:55 PM UTC-8 Andrew wrote: > Playing around with this a little more, I think that this is a bug/timing > issue in sage.misc.latex.py (or in subprocess.run, or a mac oddity since > it only

[sage-release] Re: Sage 10.3.beta0 released

Builds fine for me on OS X, both Intel and Apple Silicon. No new doctest failures. On Tuesday, December 5, 2023 at 4:26:09 PM UTC-8 Volker Braun wrote: > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > htt

[cctalk] Re: Current SOA scsi disk emulators for DEC

e/ - marketing info -- John H. Reinhardt

[cctalk] Re: Current SOA scsi disk emulators for DEC

e/ - marketing info -- John H. Reinhardt

[sage-devel] Re: Policy for disputed PRs: discussion

The original proposal allows for anyone to post to sage-devel to try to raise awareness ("Also note that an objector is welcome to attempt to bring others into the discussion on their side if they remain firmly opposed"). I prefer allowing the various participants the freedom to decide whether t

[sage-devel] Re: Policy for disputed PRs: discussion

I agree that we need a policy, and I am happy with David's proposal. A tangential follow-up to Matthias: I think that our code of conduct should be part of the distributed documentation. Should it be in the Developer's Guide? In some other existing documentation? As a standalone document? -- J

[sage-devel] Help with matroids (and more generally?), PR #36492

This post concerns https://github.com/sagemath/sage/pull/36492. The main topic of that PR is matroids about which I know almost nothing, so I am not the right person to review it. The structure of the PR perhaps opens up broader questions. The author has some new code, along with a PDF document

[sage-devel] Re: Errors with make on macOS

Try: % make distclean # remove all progress, just in case % brew install cddlib fplll gsl maxima python3 singular suite-sparse # as recommended at the end of `./configure` % ./configure Then read the output and see if it still recommends installing gsl. I hope not. Then % make On Sunday, No

Re: [sage-devel] Re: Question about make dependencies

r than > read Python docs, as it's much less fun. > > Get a life. > > > > On Tue, 14 Nov 2023, 23:19 John H Palmieri, wrote: > >> Not all Americans like to verb things so profligately. >> >> On Tuesday, November 14, 2023 at 1:15:07 PM UTC-8 Dima Pas

Re: [sage-devel] Re: Question about make dependencies

Not all Americans like to verb things so profligately. On Tuesday, November 14, 2023 at 1:15:07 PM UTC-8 Dima Pasechnik wrote: > > > On Tue, 14 Nov 2023, 20:39 Matthias Koeppe, wrote: > >> On Tuesday, November 14, 2023 at 11:39:52 AM UTC-8 Dima Pasechnik wrote: >> >> On Tue, Nov 14, 2023 at 7:22

[sage-support] Re: Integral result differ from Wolfram|Alpha

Isn't log(log(x)^2) = 2 * log(log(x))? Is this your concern, or is it the absolute value? On Monday, November 13, 2023 at 1:32:11 PM UTC-8 Bùi Gia Nghĩa wrote: > Hi! > I have used Sage Cell Server to integrate the function (ln(x)^2 - 1) / (x > * ln(x)). It should resulted in (ln(x)^2) / 2 - |ln

[sage-release] Re: Sage 10.2.rc1 released

A better link for the 3rd and 4th failures is #36631 (https://github.com/sagemath/sage/issues/36631). On Saturday, November 11, 2023 at 9:52:26 AM UTC-8 John H Palmieri wrote: > On OS X Intel, looks good. Four doctest failures, all of which have been > reported: > > sage -t --l

[sage-release] Re: Sage 10.2.rc1 released

Same on OS X Apple M2 chip. In both this and the earlier case, I ran `./configure` — no need to do `./configure --with-system-gfortran=no`. On Saturday, November 11, 2023 at 9:52:26 AM UTC-8 John H Palmieri wrote: > On OS X Intel, looks good. Four doctest failures, all of which have b

[sage-release] Re: Sage 10.2.rc1 released

On OS X Intel, looks good. Four doctest failures, all of which have been reported: sage -t --long --random-seed=120467112235779717922036180522489127126 src/sage/libs/giac/__init__.py # Timed out sage -t --long --random-seed=120467112235779717922036180522489127126 src/sage/rings/polynomial/mult

[sage-devel] Re: https://github.com/sagemath/sage/wiki/Sage-10.2-Release-Tour

Where might changes to the Sage library go? I might want to highlight #36310. On Friday, November 10, 2023 at 10:38:00 AM UTC-8 Matthias Koeppe wrote: > So far we have: > > Sage 10.2 Release Tour > > >- Live Documentation >

[sage-release] Re: Sage 10.2.rc0 released

On OS X, 10.2.rc0 behaves similarly to the previous release, no new doctest failures. On Sunday, November 5, 2023 at 1:18:52 PM UTC-8 John H Palmieri wrote: > It would be great if #36599 could be merged in the 10.2 cycle: this should > allow scipy to build with recent versions o

  1   2   3   4   5   6   7   8   9   10   >