Re: [sage-devel] Re: export SAGE_ROOT from '$SAGE_LOCAL/bin/sage'

[Matthias Koeppe]

On Monday, May 16, 2022 at 9:12:53 PM UTC-7 hohoa...@gmail.com wrote:

> Is it this snippet, would you please elaborate?
>
> 
> # Make sure that SAGE_ROOT is either an absolute physical directory name
> # or empty.
> if [ -n "$SAGE_ROOT" ]; then
> export SAGE_ROOT=$(cd "$SAGE_ROOT" 2>/dev/null && pwd -P)
> fi
> 
>

Yes. You asked what happens when SAGE_ROOT has disappeared.
Well, in this case, after these lines are run, SAGE_ROOT will be empty.

BTW, it is rather confusing to see in '$SAGE_LOCAL/bin/sage':
>
> if [ -f "${SELF}-env-config" ]; then
> # As of Trac #22731, sage-env-config is optional.
> . "${SELF}-env-config" >&2
> fi
>
> again export SAGE_ROOT and SAGE_LOCAL (same as in the original question, 
> about 10 lines below)
>
 
It is actually $SAGE_VENV/bin/sage. When this script is invoked directly, 
it does not know about SAGE_ROOT. It first sources 
$SAGE_LOCAL/bin/sage-config to find the value of SAGE_ROOT and SAGE_LOCAL. 
Afterwards it sources $SAGE_LOCAL/bin/sage-env-config (and then 
$SAGE_LOCAL/bin/sage-env) to find the value of SAGE_ROOT and SAGE_LOCAL.

There is some redundancy there. sage-config is relatively new (it was added 
in https://trac.sagemath.org/ticket/29038), and it might be that in some 
downstream packaging of Sage it is not installed. sage-env-config has been 
around for a longer time, and eventually we may want to get rid of it.
See https://trac.sagemath.org/ticket/21707 for an overview of this work.
 

> Is it a prerequisite that $SAGE_ROOT be part of the installation and it 
> must stay as long as $SAGE_LOCAL is around?
>

No, it is not required. SAGE_LOCAL is a self-contained installation 
hierarchy. If you use "configure --prefix=..." to set SAGE_LOCAL to a 
directory outside of SAGE_ROOT, then it is OK to delete SAGE_ROOT 
afterwards. After you delete it, of course the commands that need 
SAGE_ROOT, such as "sage -i" for package installation, are no longer 
available.

-- 
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/msgid/sage-devel/05b0133d-c125-4f5c-b8b7-eeb3a9b63561n%40googlegroups.com.

Re: [sage-devel] Re: export SAGE_ROOT from '$SAGE_LOCAL/bin/sage'

[ph h]

Hi,

Is it this snippet, would you please elaborate?


# Make sure that SAGE_ROOT is either an absolute physical directory name
# or empty.
if [ -n "$SAGE_ROOT" ]; then
export SAGE_ROOT=$(cd "$SAGE_ROOT" 2>/dev/null && pwd -P)
fi


BTW, it is rather confusing to see in '$SAGE_LOCAL/bin/sage':

if [ -f "${SELF}-env-config" ]; then
# As of Trac #22731, sage-env-config is optional.
. "${SELF}-env-config" >&2
fi

again export SAGE_ROOT and SAGE_LOCAL (same as in the original question,
about 10 lines below)

Many references to $SAGE_ROOT in  '$SAGE_LOCAL/bin/sage'.

Is it a prerequisite that $SAGE_ROOT be part of the installation and it
must stay as long as $SAGE_LOCAL is around?
Or these parts of  '$SAGE_LOCAL/bin/sage'. should be factored out?

Thank you for your help.

Regards,

phiho







On Mon, May 16, 2022 at 11:14 PM Matthias Koeppe 
wrote:

> On Monday, May 16, 2022 at 8:07:48 PM UTC-7 hohoa...@gmail.com wrote:
>
>> Please advise the use of SAGE_ROOT when it is exported
>> from  '$SAGE_LOCAL/bin/sage':
>>
>> # Determine SAGE_ROOT, SAGE_LOCAL, and SAGE_VENV.
>> unset SAGE_VENV
>> if [ -x "${SELF}-config" ]; then
>> # optional sage-config console script, installed by sage_conf
>> export SAGE_ROOT=$("${SELF}-config" SAGE_ROOT)
>> export SAGE_LOCAL=$("${SELF}-config" SAGE_LOCAL)
>> fi
>>
>> What if $SAGE_ROOT was deleted?
>>
>
> see src/bin/sage-env around line 111
>
>
>
>
> --
> 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/msgid/sage-devel/68b66f75-0fec-4e9b-bca3-e2ee04bde2e8n%40googlegroups.com
> 
> .
>

-- 
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/msgid/sage-devel/CALZQg1ZAVyzCJe8wtBmh02W9Z29XojDP0dH2fNvHqhU1sj1r8g%40mail.gmail.com.

[sage-devel] Re: export SAGE_ROOT from '$SAGE_LOCAL/bin/sage'

[Matthias Koeppe]

On Monday, May 16, 2022 at 8:07:48 PM UTC-7 hohoa...@gmail.com wrote:

> Please advise the use of SAGE_ROOT when it is exported 
> from  '$SAGE_LOCAL/bin/sage':
>
> # Determine SAGE_ROOT, SAGE_LOCAL, and SAGE_VENV.
> unset SAGE_VENV
> if [ -x "${SELF}-config" ]; then
> # optional sage-config console script, installed by sage_conf
> export SAGE_ROOT=$("${SELF}-config" SAGE_ROOT)
> export SAGE_LOCAL=$("${SELF}-config" SAGE_LOCAL)
> fi
>
> What if $SAGE_ROOT was deleted?
>

see src/bin/sage-env around line 111
 

 

-- 
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/msgid/sage-devel/68b66f75-0fec-4e9b-bca3-e2ee04bde2e8n%40googlegroups.com.

[sage-devel] export SAGE_ROOT from '$SAGE_LOCAL/bin/sage'

[ph h]

Dear All,

Please advise the use of SAGE_ROOT when it is exported 
from  '$SAGE_LOCAL/bin/sage':

# Determine SAGE_ROOT, SAGE_LOCAL, and SAGE_VENV.
unset SAGE_VENV
if [ -x "${SELF}-config" ]; then
# optional sage-config console script, installed by sage_conf
export SAGE_ROOT=$("${SELF}-config" SAGE_ROOT)
export SAGE_LOCAL=$("${SELF}-config" SAGE_LOCAL)
fi

What if $SAGE_ROOT was deleted?

Thank you for your help.

Regards,

phiho

-- 
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/msgid/sage-devel/ed4f9616-5cb6-4411-9c00-8340547e91e4n%40googlegroups.com.

Re: [sage-devel] file reported missing during install

[François Bissey]

And trivial https://trac.sagemath.org/ticket/33859 is ready for review.

> On 17/05/2022, at 12:24, François Bissey  wrote:
> 
> Right, I’ll open a ticket for that.
> 
>> On 17/05/2022, at 12:11, Matthias Koeppe  wrote:
>> 
>> It looks like this directory was removed in #27155, so this line can be 
>> removed from MANIFEST.in
>> 
>> 
>> On Monday, May 16, 2022 at 4:31:50 PM UTC-7 François Bissey wrote:
>> Hi, 
>> 
>> I have noticed it before but I have only started to wonder about it while 
>> preparing the 9.6 release for Gentoo. 
>> During the install phase while the wheel is being prepared I have the 
>> following messages 
>> 
>> listing git files failed - pretending there aren't any 
>> warning: no files found matching '*.hh' anywhere in distribution 
>> warning: no files found matching '*.inc' anywhere in distribution 
>> no previously-included directories found matching '.tox' 
>> warning: no directories found matching 'sage/libs/gap/test' 
>> no previously-included directories found matching 'sage_setup' 
>> * Installing the wheel to 
>> /var/tmp/portage/sci-mathematics/sage-9.6/work/sagemath-standard-9.6-python3_10/install
>>  
>> 
>> Nothing really surprising except for that “sage/libs/gap/test” directory 
>> seemingly coming out of nowhere. 
>> 
>> Inspecting the source in git, it seems to come from src/MANIFEST.in 
>> src/MANIFEST.in:graft sage/libs/gap/test 
>> which ultimately is shipped inside the sage math-standard sdist as its 
>> regular MANIFEST.in file. 
>> Is this something that should be removed or that is actually incorrect? 
>> There is no such folder but there are two files called 
>> sage/libs/gap/test.py 
>> sage/libs/gap/test_long.py 
>> in the sources and they are installed as regular python files as part of 
>> sagemath-standard. 
>> 
>> François
>> 
>> -- 
>> 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/msgid/sage-devel/d5a4df47-5098-489a-8910-2ddfc656144en%40googlegroups.com.
> 

-- 
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/msgid/sage-devel/D35A4FBC-EE74-4707-9C06-6973F5A68AE3%40gmail.com.

Re: [sage-devel] file reported missing during install

[François Bissey]

Right, I’ll open a ticket for that.

> On 17/05/2022, at 12:11, Matthias Koeppe  wrote:
> 
> It looks like this directory was removed in #27155, so this line can be 
> removed from MANIFEST.in
> 
> 
> On Monday, May 16, 2022 at 4:31:50 PM UTC-7 François Bissey wrote:
> Hi, 
> 
> I have noticed it before but I have only started to wonder about it while 
> preparing the 9.6 release for Gentoo. 
> During the install phase while the wheel is being prepared I have the 
> following messages 
> 
> listing git files failed - pretending there aren't any 
> warning: no files found matching '*.hh' anywhere in distribution 
> warning: no files found matching '*.inc' anywhere in distribution 
> no previously-included directories found matching '.tox' 
> warning: no directories found matching 'sage/libs/gap/test' 
> no previously-included directories found matching 'sage_setup' 
> * Installing the wheel to 
> /var/tmp/portage/sci-mathematics/sage-9.6/work/sagemath-standard-9.6-python3_10/install
>  
> 
> Nothing really surprising except for that “sage/libs/gap/test” directory 
> seemingly coming out of nowhere. 
> 
> Inspecting the source in git, it seems to come from src/MANIFEST.in 
> src/MANIFEST.in:graft sage/libs/gap/test 
> which ultimately is shipped inside the sage math-standard sdist as its 
> regular MANIFEST.in file. 
> Is this something that should be removed or that is actually incorrect? There 
> is no such folder but there are two files called 
> sage/libs/gap/test.py 
> sage/libs/gap/test_long.py 
> in the sources and they are installed as regular python files as part of 
> sagemath-standard. 
> 
> François
> 
> -- 
> 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/msgid/sage-devel/d5a4df47-5098-489a-8910-2ddfc656144en%40googlegroups.com.

-- 
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/msgid/sage-devel/41943245-254A-41C0-9902-B47BF0960A91%40gmail.com.

[sage-devel] Re: file reported missing during install

[Matthias Koeppe]

It looks like this directory was removed in #27155, so this line can be 
removed from MANIFEST.in


On Monday, May 16, 2022 at 4:31:50 PM UTC-7 François Bissey wrote:

> Hi,
>
> I have noticed it before but I have only started to wonder about it while 
> preparing the 9.6 release for Gentoo.
> During the install phase while the wheel is being prepared I have the 
> following messages
>
> listing git files failed - pretending there aren't any
> warning: no files found matching '*.hh' anywhere in distribution
> warning: no files found matching '*.inc' anywhere in distribution
> no previously-included directories found matching '.tox'
> warning: no directories found matching 'sage/libs/gap/test'
> no previously-included directories found matching 'sage_setup'
> * Installing the wheel to 
> /var/tmp/portage/sci-mathematics/sage-9.6/work/sagemath-standard-9.6-python3_10/install
>
> Nothing really surprising except for that “sage/libs/gap/test” directory 
> seemingly coming out of nowhere.
>
> Inspecting the source in git, it seems to come from src/MANIFEST.in
> src/MANIFEST.in:graft sage/libs/gap/test
> which ultimately is shipped inside the sage math-standard sdist as its 
> regular MANIFEST.in file.
> Is this something that should be removed or that is actually incorrect? 
> There is no such folder but there are two files called
> sage/libs/gap/test.py
> sage/libs/gap/test_long.py
> in the sources and they are installed as regular python files as part of 
> sagemath-standard.
>
> François

-- 
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/msgid/sage-devel/d5a4df47-5098-489a-8910-2ddfc656144en%40googlegroups.com.

[sage-devel] file reported missing during install

[François Bissey]

Hi,

I have noticed it before but I have only started to wonder about it while 
preparing the 9.6 release for Gentoo.
During the install phase while the wheel is being prepared I have the following 
messages

listing git files failed - pretending there aren't any
warning: no files found matching '*.hh' anywhere in distribution
warning: no files found matching '*.inc' anywhere in distribution
no previously-included directories found matching '.tox'
warning: no directories found matching 'sage/libs/gap/test'
no previously-included directories found matching 'sage_setup'
 *   Installing the wheel to 
/var/tmp/portage/sci-mathematics/sage-9.6/work/sagemath-standard-9.6-python3_10/install

Nothing really surprising except for that “sage/libs/gap/test” directory 
seemingly coming out of nowhere.

Inspecting the source in git, it seems to come from src/MANIFEST.in
src/MANIFEST.in:graft   sage/libs/gap/test
which ultimately is shipped inside the sage math-standard sdist as its regular 
MANIFEST.in file.
Is this something that should be removed or that is actually incorrect? There 
is no such folder but there are two files called
sage/libs/gap/test.py
sage/libs/gap/test_long.py
in the sources and they are installed as regular python files as part of 
sagemath-standard.

François

-- 
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/msgid/sage-devel/C3489833-854D-49C2-9AC0-66EB9CB0D875%40gmail.com.

[sage-devel] Re: Error when installing Sage from source

[Matthias Koeppe]

Please take a look at the notes for the Apple Silicon platform 
at https://trac.sagemath.org/wiki/ReleaseTours/sage-9.6#Sources
If the problem persists, please send the top-level config.log file

On Saturday, May 14, 2022 at 1:14:12 PM UTC-7 ijoll...@gmail.com wrote:

> Hi, 
>
> I am very new to Sage, and software development in particular. I recently 
> tried cloning the GitHub repo, and installing Sage from root. However, on 
> running make, I failed. I was wondering if some assitance could be 
> provided. Here is the error message: 
>
> [ppl-1.2.p1] Package 'ppl' is currently not installed
> [ppl-1.2.p1] No legacy uninstaller found for 'ppl'; nothing to do
> [ppl-1.2.p1] Configuring ppl-1.2.p1
> [ppl-1.2.p1] configure: WARNING: unrecognized options: 
> --disable-maintainer-mode
> [ppl-1.2.p1] checking build system type... Invalid configuration 
> `arm64-apple-darwin20.0.0': machine `arm64-apple' not recognized
> [ppl-1.2.p1] configure: error: /bin/bash ./config.sub 
> arm64-apple-darwin20.0.0 failed
> [ppl-1.2.p1] checking build system type... Invalid configuration 
> `arm64-apple-darwin20.0.0': machine `arm64-apple' not recognized
> [ppl-1.2.p1] configure: error: /bin/bash ./config.sub 
> arm64-apple-darwin20.0.0 failed
> [ppl-1.2.p1] 
> *
> [ppl-1.2.p1] Error configuring ppl-1.2.p1 See the file
> [ppl-1.2.p1] 
> /Users/ishaanjolly/Programs/sage/local/var/tmp/sage/build/ppl-1.2.p1/src/config.log
> [ppl-1.2.p1] for details.
> [ppl-1.2.p1] 
> *
> [ppl-1.2.p1] Error configuring PPL with both C and C++ interfaces, trying
> [ppl-1.2.p1] again with only the C++ interface.
> [ppl-1.2.p1] Configuring ppl-1.2.p1
> [ppl-1.2.p1] configure: WARNING: unrecognized options: 
> --disable-maintainer-mode
> [ppl-1.2.p1] checking build system type... Invalid configuration 
> `arm64-apple-darwin20.0.0': machine `arm64-apple' not recognized
> [ppl-1.2.p1] configure: error: /bin/bash ./config.sub 
> arm64-apple-darwin20.0.0 failed
> [ppl-1.2.p1] checking build system type... Invalid configuration 
> `arm64-apple-darwin20.0.0': machine `arm64-apple' not recognized
> [ppl-1.2.p1] configure: error: /bin/bash ./config.sub 
> arm64-apple-darwin20.0.0 failed
> [ppl-1.2.p1] 
> *
> [ppl-1.2.p1] Error configuring ppl-1.2.p1 See the file
> [ppl-1.2.p1] 
> /Users/ishaanjolly/Programs/sage/local/var/tmp/sage/build/ppl-1.2.p1/src/config.log
> [ppl-1.2.p1] for details.
> [ppl-1.2.p1] 
> *
> [ppl-1.2.p1] 
> [ppl-1.2.p1] real0m1.080s
> [ppl-1.2.p1] user0m0.244s
> [ppl-1.2.p1] sys0m0.302s
> [ppl-1.2.p1] 
> 
> [ppl-1.2.p1] Error installing package ppl-1.2.p1
> [ppl-1.2.p1] 
> 
> [ppl-1.2.p1] Please email sage-devel (
> http://groups.google.com/group/sage-devel)
> [ppl-1.2.p1] explaining the problem and including the log files
> [ppl-1.2.p1]   /Users/ishaanjolly/Programs/sage/logs/pkgs/ppl-1.2.p1.log
> [ppl-1.2.p1] and
> [ppl-1.2.p1]   /Users/ishaanjolly/Programs/sage/config.log
> [ppl-1.2.p1] Describe your computer, operating system, etc.
> [ppl-1.2.p1] If you want to try to fix the problem yourself, *don't* just 
> cd to
> [ppl-1.2.p1] 
> /Users/ishaanjolly/Programs/sage/local/var/tmp/sage/build/ppl-1.2.p1 and 
> type 'make' or whatever is appropriate.
> [ppl-1.2.p1] Instead, the following commands setup all environment 
> variables
> [ppl-1.2.p1] correctly and load a subshell for you to debug the error:
> [ppl-1.2.p1]   (cd 
> '/Users/ishaanjolly/Programs/sage/local/var/tmp/sage/build/ppl-1.2.p1' && 
> '/Users/ishaanjolly/Programs/sage/sage' --buildsh)
> [ppl-1.2.p1] When you are done debugging, you can type "exit" to leave the 
> subshell.
> [ppl-1.2.p1] 
> 
> make[4]: *** [ppl-SAGE_LOCAL-no-deps] Error 1
> make[3]: *** 
> [/Users/ishaanjolly/Programs/sage/local/var/lib/sage/installed/ppl-1.2.p1] 
> Error 2
> make[2]: *** [all-start] Error 2
>
> real3m17.156s
> user2m26.222s
> sys0m18.146s
> ***
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: ppl-1.2.p1
>   last build time: 14 May 20:50
>   log file:   
>  /Users/ishaanjolly/Programs/sage/logs/pkgs/ppl-1.2.p1.log
>   build directory: 
> /Users/ishaanjolly/Programs/sage/local/var/tmp/sage/build/ppl-1.2.p1
>
> It is safe to delete any log files and build directories, but they
> contain information that is helpful for debugging build problems.
> 

Re: [sage-devel] Re: Run the actual Sage script

[ph h]

Hi,

"""
We change the bootstrap scripts so that they invoke
build/bin/sage-package directly
instead of going through the SAGE_ROOT/sage script.
"""

This is great news, a big time saver. Thank you so much.
Until then,  this hitchhiker needs to restore the original
'$SAGE_ROOT/sage' before she can 'make configure' ('bootstrap' requires
that original 'sage') while testing 'configure.ac'

Best regards,

phiho


On Mon, May 16, 2022 at 12:24 PM Matthias Koeppe 
wrote:

> On Monday, May 16, 2022 at 1:35:37 AM UTC-7 hohoa...@gmail.com wrote:
>
>> [...]  $SAGE_ROOT/sage [...]
>>
>
> The positively reviewed tickets https://trac.sagemath.org/ticket/33786
> and https://trac.sagemath.org/ticket/33787 make changes to this script.
> You may find these changes and the discussion on the ticket interesting.
>
> https://trac.sagemath.org/ticket/33852 makes other changes related to the
> script. It needs review.
>
> --
> 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/msgid/sage-devel/ec09cac9-4037-477b-968c-25f2ded19d54n%40googlegroups.com
> 
> .
>

-- 
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/msgid/sage-devel/CALZQg1aRaEpNsCBedkC6yr558VFRH%2BhqP9y9OwQf5n-4rJ37RQ%40mail.gmail.com.

[sage-devel] Re: Run the actual Sage script

[Matthias Koeppe]

On Monday, May 16, 2022 at 1:35:37 AM UTC-7 hohoa...@gmail.com wrote:

> [...]  $SAGE_ROOT/sage [...]
>

The positively reviewed tickets https://trac.sagemath.org/ticket/33786 
and https://trac.sagemath.org/ticket/33787 make changes to this script. You 
may find these changes and the discussion on the ticket interesting.

https://trac.sagemath.org/ticket/33852 makes other changes related to the 
script. It needs review.

-- 
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/msgid/sage-devel/ec09cac9-4037-477b-968c-25f2ded19d54n%40googlegroups.com.

[sage-devel] Re: Memory Leak in canonical_label with bliss?

[Antonio Rojas]

El lunes, 16 de mayo de 2022 a las 17:34:14 UTC+2, Ricardo Buring escribió:

> Specifically bliss::AbstractGraph::canonical_form calls 
> bliss::AbstractGraph::search, which sometimes calls 
> bliss::Partition::cr_init without calling bliss::Partition::cr_free, due 
> to a (conditional) early return.
> This leak is fixed in the latest upstream release available from 
> https://users.aalto.fi/~tjunttil/bliss/
>

Updating bliss is tracked at #33010 (and needs help) 

-- 
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/msgid/sage-devel/1ca23836-d644-4b8d-848e-818aae02cce7n%40googlegroups.com.

Re: [sage-devel] (cy)PARI in Parallel, Heisenbugs, and Merging Policy

[Dima Pasechnik]

On Mon, May 16, 2022 at 8:03 AM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> I would say that code with parallel computations + cypari2 should not
> be merged (as cypari2 does not support it).

is it parallel multiprocessing, or parallel multithreading?

>
> If you need parallel + PARI then use the C library directly with the
> appropriate threads locks.
>
> If the problem comes from somewhere else, then it would better be sorted
> out.
>
> Best
> Vincent
>
> Le 16/05/2022 à 06:42, 'Travis Scrimshaw' via sage-devel a écrit :
> > That sure seems like it. So what should we do about the ticket? Would there
> > be opposition to merging this piece of code, as there doesn't seem like
> > there is a fix coming for the likely underlying cypari bug anytime soon?
> >
> > Best,
> > Travis
> >
> >
> > On Sunday, May 15, 2022 at 4:14:31 PM UTC+9 vdelecroix wrote:
> >
> >> Probably related to https://github.com/sagemath/cypari2/issues/107 ?
> >>
> >> Le 15/05/2022 à 05:06, 'Travis Scrimshaw' via sage-devel a écrit :
> >>> Hi everyone,
> >>> On ticket #30423 , Dan, Willie,
> >>> and I have been working on a parallel-computation based implementation
> >> for
> >>> computing F-matrices that are used in math physics. However, we have been
> >>> seeing some doctest failures sporadically that involve segfaults and
> >>> linked-list corruption from (cy)PARI. Here are the logs from testing with
> >>> the first and the last having full tracebacks.
> >>>
> >>> http://sporadic.stanford.edu/badlog-match
> >>> http://sporadic.stanford.edu/badlog
> >>> http://sporadic.stanford.edu/badlog1
> >>> http://sporadic.stanford.edu/badlog2
> >>> http://sporadic.stanford.edu/badlog3
> >>>
> >>> The first question would be if anyone has an idea about what is causing
> >>> this. I have this impression that PARI is thread-safe, but I am wondering
> >>> if cypari is also thread/parallel-safe or if there are any specific
> >> things
> >>> that we should be careful about. (We’ve already had to work around a
> >>> pickling issue with polynomials IIRC.)
> >>>
> >>> Second question is that because this is a Heisenbug and I suspect it is
> >>> something upstream (and so far, nobody has been able to reproducing it
> >>> during an interactive version of Sage), I was wondering what the policy
> >>> would be for merging the ticket. I recall in the past that we have merged
> >>> tickets with Heisenbugs with followup tickets noting the behavior, but I
> >> am
> >>> not 100% sure about that (and I wouldn’t necessarily know how to find any
> >>> explicit examples). I was wondering if we could merge the ticket in an
> >>> early beta version so that many people/systems can test it to see if it
> >>> becomes more reproducible; of course this is assuming that the build bots
> >>> are not consistent in reproducing this. Should we just mark any offending
> >>> test(s) as “# known bug” and is there some general policy about this?
> >>>
> >>> Thanks,
> >>> Travis
> >>>
> >>>
> >>
> >
>
> --
> 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/msgid/sage-devel/fd05e9f5-52b2-f2f8-bc02-c968c0a70e79%40gmail.com.

-- 
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/msgid/sage-devel/CAAWYfq0B0H2E3JG-yPG%2B%3Dx-ZEutpbbH_NAW_tRD%3DJG9MPqrUiA%40mail.gmail.com.

Re: [sage-devel] Run the actual Sage script

[ph h]

P.S: Sorry, there was a typo,  "$SAGE_LOCAL/sage" should read
"$SAGE_LOCAL/bin/sage"

On Mon, May 16, 2022 at 4:35 AM ph h  wrote:

> Dear All,
>
> Please find appended below a snippet from  $SAGE_ROOT/sage.
>
> Would it be nice if "$SAGE_LOCAL/sage" could be used without assumptions
> instead of "$SAGE_ROOT/local/bin/sage" with the assumption that 'SAGE_LOCAL
> is the "local" subdirectory'
>
> BTW, should "$SAGE_LOCAL/sage"  be the first choice if it is ready to run?
>
> Thank you for your enlightenment
>
> Regards,
>
> phiho
>
> <$SAGE_ROOT/sage>
> # Run the actual Sage script
> if [ -x "$SAGE_ROOT/src/bin/sage" ]; then
> exec "$SAGE_ROOT/src/bin/sage" "$@"
> elif [ -x "$SAGE_ROOT/local/bin/sage" ]; then # if in a stripped binary
> # Note in this case we assume that SAGE_LOCAL is the "local"
> subdirectory
> exec "$SAGE_ROOT/local/bin/sage" "$@"
> else
> echo >&2 "$0: no Sage installation found in \$SAGE_ROOT=$SAGE_ROOT"
> exit 1
> fi
> 
>
> --
> 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/msgid/sage-devel/8a705a39-977c-4fcb-b1f4-5d38b490f3e1n%40googlegroups.com
> 
> .
>

-- 
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/msgid/sage-devel/CALZQg1bkirqCC%2BLc8L8cvSJtSo_VXdhUc3anMBHt2ackW4F8JA%40mail.gmail.com.

[sage-devel] Run the actual Sage script

[ph h]

Dear All,

Please find appended below a snippet from  $SAGE_ROOT/sage.

Would it be nice if "$SAGE_LOCAL/sage" could be used without assumptions 
instead of "$SAGE_ROOT/local/bin/sage" with the assumption that 'SAGE_LOCAL 
is the "local" subdirectory'

BTW, should "$SAGE_LOCAL/sage"  be the first choice if it is ready to run?

Thank you for your enlightenment

Regards,

phiho

<$SAGE_ROOT/sage>
# Run the actual Sage script
if [ -x "$SAGE_ROOT/src/bin/sage" ]; then
exec "$SAGE_ROOT/src/bin/sage" "$@"
elif [ -x "$SAGE_ROOT/local/bin/sage" ]; then # if in a stripped binary
# Note in this case we assume that SAGE_LOCAL is the "local" 
subdirectory
exec "$SAGE_ROOT/local/bin/sage" "$@"
else
echo >&2 "$0: no Sage installation found in \$SAGE_ROOT=$SAGE_ROOT"
exit 1
fi


-- 
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/msgid/sage-devel/8a705a39-977c-4fcb-b1f4-5d38b490f3e1n%40googlegroups.com.

Re: [sage-devel] (cy)PARI in Parallel, Heisenbugs, and Merging Policy

[Vincent Delecroix]

I would say that code with parallel computations + cypari2 should not
be merged (as cypari2 does not support it).

If you need parallel + PARI then use the C library directly with the
appropriate threads locks.

If the problem comes from somewhere else, then it would better be sorted
out.

Best
Vincent

Le 16/05/2022 à 06:42, 'Travis Scrimshaw' via sage-devel a écrit :

That sure seems like it. So what should we do about the ticket? Would there
be opposition to merging this piece of code, as there doesn't seem like
there is a fix coming for the likely underlying cypari bug anytime soon?

Best,
Travis


On Sunday, May 15, 2022 at 4:14:31 PM UTC+9 vdelecroix wrote:


Probably related to https://github.com/sagemath/cypari2/issues/107 ?

Le 15/05/2022 à 05:06, 'Travis Scrimshaw' via sage-devel a écrit :

Hi everyone,
On ticket #30423 , Dan, Willie,
and I have been working on a parallel-computation based implementation

for

computing F-matrices that are used in math physics. However, we have been
seeing some doctest failures sporadically that involve segfaults and
linked-list corruption from (cy)PARI. Here are the logs from testing with
the first and the last having full tracebacks.

http://sporadic.stanford.edu/badlog-match
http://sporadic.stanford.edu/badlog
http://sporadic.stanford.edu/badlog1
http://sporadic.stanford.edu/badlog2
http://sporadic.stanford.edu/badlog3

The first question would be if anyone has an idea about what is causing
this. I have this impression that PARI is thread-safe, but I am wondering
if cypari is also thread/parallel-safe or if there are any specific

things

that we should be careful about. (We’ve already had to work around a
pickling issue with polynomials IIRC.)

Second question is that because this is a Heisenbug and I suspect it is
something upstream (and so far, nobody has been able to reproducing it
during an interactive version of Sage), I was wondering what the policy
would be for merging the ticket. I recall in the past that we have merged
tickets with Heisenbugs with followup tickets noting the behavior, but I

am

not 100% sure about that (and I wouldn’t necessarily know how to find any
explicit examples). I was wondering if we could merge the ticket in an
early beta version so that many people/systems can test it to see if it
becomes more reproducible; of course this is assuming that the build bots
are not consistent in reproducing this. Should we just mark any offending
test(s) as “# known bug” and is there some general policy about this?

Thanks,
Travis








--
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/msgid/sage-devel/fd05e9f5-52b2-f2f8-bc02-c968c0a70e79%40gmail.com.