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

2020-08-20 Thread Dima Pasechnik 


On Wednesday, August 19, 2020 at 3:04:18 PM UTC+1 erik@gmail.com wrote:

> On Friday, August 14, 2020 at 1:44:38 PM UTC+2 david@gmail.com wrote:
>
>> Same here on a fresh clone with macOS 10.15.16
>>
>>
>> [dochtml] Building en/constructions.
>> [dochtml] 
>> [dochtml] [construct] building [html]: targets for 16 source files that 
>> are out of date
>> [dochtml] [construct] updating environment: [new config] 16 added, 0 
>> changed, 0 removed
>> ^C[dochtml] Error building the documentation.
>> [dochtml] Traceback (most recent call last):
>> [dochtml]   File 
>> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/runpy.py",
>>  
>> line 193, in _run_module_as_main
>> [dochtml] "__main__", mod_spec)
>> [dochtml]   File 
>> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/runpy.py",
>>  
>> line 85, in _run_code
>> [dochtml] exec(code, run_globals)
>> [dochtml]   File 
>> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__main__.py",
>>  
>> line 2, in 
>> [dochtml] main()
>> [dochtml]   File 
>> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
>>  
>> line 1721, in main
>> [dochtml] builder()
>> [dochtml]   File 
>> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
>>  
>> line 337, in _wrapper
>> [dochtml] build_many(build_other_doc, L)
>> [dochtml]   File 
>> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
>>  
>> line 281, in build_many
>> [dochtml] _build_many(target, args, processes=NUM_THREADS)
>> [dochtml]   File 
>> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/utils.py",
>>  
>> line 263, in build_many
>> [dochtml] waited_pid, waited_exitcode = wait_for_one()
>> [dochtml]   File 
>> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/utils.py",
>>  
>> line 179, in wait_for_one
>> [dochtml] pid, sts = os.wait()
>> [dochtml]   File "src/cysignals/signals.pyx", line 320, in 
>> cysignals.signals.python_check_interrupt
>> [dochtml] KeyboardInterrupt
>> [dochtml] 
>> [dochtml] Note: incremental documentation builds sometimes cause 
>> spurious
>> [dochtml] error messages. To be certain that these are real errors, 
>> run
>> [dochtml] "make doc-clean" first and try again.
>> make[3]: *** [doc-html] Error 1
>> make[2]: *** [all-start] Interrupt: 2
>> make[1]: *** [all-start] Interrupt: 2
>> make: *** [all] Interrupt: 2
>>
>>
>>
> As I noted at [1], this implies that one or more of the docbuilds are 
> running some code that hangs forever, so it would help narrow it down by 
> finding out what code it's running to cause a hang.  Normally in docbuilds 
> the most likely code to run will be some plotting code, so you can try to 
> take the plot code present in the relevant documentation pages, run it, and 
> see if it hangs.  Chances are if you run it in a single process it might 
> *not* hang--frequently this happens only in a forked subprocess.  So you 
> can try something like:
>
> from multiprocessing import Process
> p = Process(target=)
> p.start()
>
> and see if it hangs. I've often found this to be the case with calls to 
> np.dot(), which matpotlib uses sometimes to perform various 
> transformations, and which in turn often results in a call to a 
> multi-threaded OpenBLAS function which are sometimes buggy.
>
> As an aside, I would like to make the parallel doc build code more robust 
> to this kind of hang, but it's hard to say exactly what the right solution 
> is (I know more or less what the technical solution is, but I mean more the 
> UX solution).  Because as far as the docbuild code is concerned, it doesn't 
> know that the process is "hung".  It's just taking however long it needs to 
> take, and the code will wait for it to finish.  Perhaps we could implement 
> some kind of timeout to kill docbuild processes that are taking too long 
> (but what should the timeout be)? Or report back to the user exactly which 
> docbuilds are still running (like, a log message at some interval) so that 
> the user can decide whether or not to take action.
>

I found out that the problem is due to OpenMP, see 
https://trac.sagemath.org/ticket/30351#comment: 
50
The workaround (or perhaps the only way to proceed, I don't know) is to set 
env.var. OMP_NUM_THREADS=1

 

>
> [1] https://trac.sagemath.org/ticket/30351#comment:40 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/017886ad-d707-45d1-ba42-d97422909385n%40googlegroups.com.

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

2020-08-19 Thread E. Madison Bray 
On Friday, August 14, 2020 at 1:44:38 PM UTC+2 david@gmail.com wrote:

> Same here on a fresh clone with macOS 10.15.16
>
>
> [dochtml] Building en/constructions.
> [dochtml] 
> [dochtml] [construct] building [html]: targets for 16 source files that 
> are out of date
> [dochtml] [construct] updating environment: [new config] 16 added, 0 
> changed, 0 removed
> ^C[dochtml] Error building the documentation.
> [dochtml] Traceback (most recent call last):
> [dochtml]   File 
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/runpy.py",
>  
> line 193, in _run_module_as_main
> [dochtml] "__main__", mod_spec)
> [dochtml]   File 
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/runpy.py",
>  
> line 85, in _run_code
> [dochtml] exec(code, run_globals)
> [dochtml]   File 
> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__main__.py",
>  
> line 2, in 
> [dochtml] main()
> [dochtml]   File 
> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
>  
> line 1721, in main
> [dochtml] builder()
> [dochtml]   File 
> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
>  
> line 337, in _wrapper
> [dochtml] build_many(build_other_doc, L)
> [dochtml]   File 
> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
>  
> line 281, in build_many
> [dochtml] _build_many(target, args, processes=NUM_THREADS)
> [dochtml]   File 
> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/utils.py",
>  
> line 263, in build_many
> [dochtml] waited_pid, waited_exitcode = wait_for_one()
> [dochtml]   File 
> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/utils.py",
>  
> line 179, in wait_for_one
> [dochtml] pid, sts = os.wait()
> [dochtml]   File "src/cysignals/signals.pyx", line 320, in 
> cysignals.signals.python_check_interrupt
> [dochtml] KeyboardInterrupt
> [dochtml] 
> [dochtml] Note: incremental documentation builds sometimes cause 
> spurious
> [dochtml] error messages. To be certain that these are real errors, run
> [dochtml] "make doc-clean" first and try again.
> make[3]: *** [doc-html] Error 1
> make[2]: *** [all-start] Interrupt: 2
> make[1]: *** [all-start] Interrupt: 2
> make: *** [all] Interrupt: 2
>
>
>
As I noted at [1], this implies that one or more of the docbuilds are 
running some code that hangs forever, so it would help narrow it down by 
finding out what code it's running to cause a hang.  Normally in docbuilds 
the most likely code to run will be some plotting code, so you can try to 
take the plot code present in the relevant documentation pages, run it, and 
see if it hangs.  Chances are if you run it in a single process it might 
*not* hang--frequently this happens only in a forked subprocess.  So you 
can try something like:

from multiprocessing import Process
p = Process(target=)
p.start()

and see if it hangs. I've often found this to be the case with calls to 
np.dot(), which matpotlib uses sometimes to perform various 
transformations, and which in turn often results in a call to a 
multi-threaded OpenBLAS function which are sometimes buggy.

As an aside, I would like to make the parallel doc build code more robust 
to this kind of hang, but it's hard to say exactly what the right solution 
is (I know more or less what the technical solution is, but I mean more the 
UX solution).  Because as far as the docbuild code is concerned, it doesn't 
know that the process is "hung".  It's just taking however long it needs to 
take, and the code will wait for it to finish.  Perhaps we could implement 
some kind of timeout to kill docbuild processes that are taking too long 
(but what should the timeout be)? Or report back to the user exactly which 
docbuilds are still running (like, a log message at some interval) so that 
the user can decide whether or not to take action.

[1] https://trac.sagemath.org/ticket/30351#comment:40 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/2755f337-7bf1-433b-81b1-7a98d1421a8cn%40googlegroups.com.

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

2020-08-14 Thread David Coudert 
Same here on a fresh clone with macOS 10.15.16


[dochtml] Building en/constructions.
[dochtml] 
[dochtml] [construct] building [html]: targets for 16 source files that are out 
of date
[dochtml] [construct] updating environment: [new config] 16 added, 0 changed, 0 
removed
^C[dochtml] Error building the documentation.
[dochtml] Traceback (most recent call last):
[dochtml]   File 
"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/runpy.py",
 line 193, in _run_module_as_main
[dochtml] "__main__", mod_spec)
[dochtml]   File 
"/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/runpy.py",
 line 85, in _run_code
[dochtml] exec(code, run_globals)
[dochtml]   File 
"/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__main__.py",
 line 2, in 
[dochtml] main()
[dochtml]   File 
"/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
 line 1721, in main
[dochtml] builder()
[dochtml]   File 
"/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
 line 337, in _wrapper
[dochtml] build_many(build_other_doc, L)
[dochtml]   File 
"/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
 line 281, in build_many
[dochtml] _build_many(target, args, processes=NUM_THREADS)
[dochtml]   File 
"/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/utils.py",
 line 263, in build_many
[dochtml] waited_pid, waited_exitcode = wait_for_one()
[dochtml]   File 
"/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/utils.py",
 line 179, in wait_for_one
[dochtml] pid, sts = os.wait()
[dochtml]   File "src/cysignals/signals.pyx", line 320, in 
cysignals.signals.python_check_interrupt
[dochtml] KeyboardInterrupt
[dochtml] 
[dochtml] Note: incremental documentation builds sometimes cause spurious
[dochtml] error messages. To be certain that these are real errors, run
[dochtml] "make doc-clean" first and try again.
make[3]: *** [doc-html] Error 1
make[2]: *** [all-start] Interrupt: 2
make[1]: *** [all-start] Interrupt: 2
make: *** [all] Interrupt: 2



> Le 14 août 2020 à 02:43, Samuel Lelievre  a écrit :
> 
> 2020-08-13 21:59:31 UTC, Dima Pasechnik:
> OK, I tried to reproduce this on a Mac, and indeed the build hangs 
> waiting for some parallel process to finish: 
> On hitting ctrl-C, it always (the stage of the docbuild may differ though) 
> shows the following backtrace: 
> ... 
> [dochtml] KeyboardInterrupt 
> 
> The hang occurs even with `make -j1`.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/06455f10-9dd7-435d-8f7e-17f22c0f8cbco%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CF69AE00-25E2-4724-9AF2-CBE81986ABE6%40gmail.com.

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

2020-08-13 Thread 'Justin C. Walker' via sage-release 



> On Aug 10, 2020, at 15:51 , 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 
> http://www.sagemath.org/download-latest.html 

Built from fresh clones of the 9.2.b8 branch, on three macOS systems: 10.13.6 
(2019 iMac Pro, 18-core Xeon W); 10.14.6 (2017 MBP, Quad-core Core i7); and 
10.15.6 (2019 MBP, 8-core Core i9).

No problems with any of the builds, and testing (‘ptestlong’) on each completed 
with no failures.

Justin

--
Justin C. Walker, Curmudgeon at Large
Director
Institute for the Enhancement of the Director's income
---
Question 43:
What if the hokey pokey
really *is* what it’s all about?
--

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/4B93B716-DF92-43CE-93D2-B219DA278424%40mac.com.

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

2020-08-13 Thread Samuel Lelièvre 
2020-08-13 11:35 UTC, Samuel Lelièvre:
>
> Thanks! On Debian 10, success with `make`, and a few transient
> timeouts and failures for `make testalllong`.
>
> Doctesting these files individually afterwards,
> each of them gave "All tests passed!"

... but that's because when doctesting individually
I forgot to put the appropriate "--optional=...".

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAEcArF1cN5e2uo60hHk9%2BSqkUz8%3D3sb-SK%3D7Cp31R_%3DQE2VYjg%40mail.gmail.com.

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

2020-08-13 Thread Dima Pasechnik 
could it be https://trac.sagemath.org/ticket/30345 ?

On Thu, Aug 13, 2020 at 12:35 PM Samuel Lelièvre
 wrote:
>
> Le mar. 11 août 2020 à 00:51, Volker Braun  a écrit :
> >
> > As always, you can get the latest beta version from the "develop"
> > git branch. Alternatively, the self-contained source tarball is at
> > http://www.sagemath.org/download-latest.html
>
> Thanks! On Debian 10, success with `make`, and a few transient
> timeouts and failures for `make testalllong`.
>
> ```
> --
> ./sage -t --long --random-seed=0 src/sage/calculus/calculus.py  # Timed out
> ./sage -t --long --random-seed=0 src/sage/databases/findstat.py  # 17
> doctests failed
> ./sage -t --long --random-seed=0 src/sage/databases/oeis.py  # 1 doctest 
> failed
> ./sage -t --long --random-seed=0 src/sage/doctest/external.py  # Timed out
> ./sage -t --long --random-seed=0 src/sage/functions/gamma.py  # Timed out
> ./sage -t --long --random-seed=0 src/sage/interfaces/maple.py  # 15
> doctests failed
> ./sage -t --long --random-seed=0 src/sage/interfaces/interface.py  # Timed out
> ./sage -t --long --random-seed=0 src/sage/interfaces/mathematica.py  # Timed 
> out
> ./sage -t --long --random-seed=0 src/sage/interfaces/octave.py  # 3
> doctests failed
> ./sage -t --long --random-seed=0 src/sage/interfaces/scilab.py  # Timed out
> ./sage -t --long --random-seed=0 src/sage/matrix/matrix1.pyx  # Timed out
> ./sage -t --long --random-seed=0 src/sage/misc/remote_file.py  # 1
> doctest failed
> ./sage -t --long --random-seed=0 src/sage/misc/functional.py  # Timed out
> ./sage -t --long --random-seed=0
> src/sage/modules/free_module_element.pyx  # Timed out
> ./sage -t --long --random-seed=0 src/sage/plot/plot.py  # 88 doctests failed
> ./sage -t --long --random-seed=0 src/sage/plot/graphics.py  # 63 doctests 
> failed
> ./sage -t --long --random-seed=0 src/sage/symbolic/constants_c.pyx  # Timed 
> out
> ./sage -t --long --random-seed=0 src/sage/symbolic/constants.py  # Timed out
> ./sage -t --long --random-seed=0 src/sage/symbolic/expression.pyx  # Timed out
> ./sage -t --long --random-seed=0
> src/sage/symbolic/integration/integral.py  # Timed out
> ./sage -t --long --random-seed=0 src/sage/tests/benchmark.py  # Timed out
> ./sage -t --long --random-seed=0
> src/doc/en/constructions/interface_issues.rst  # 1 doctest failed
> ./sage -t --long --random-seed=0
> src/doc/en/constructions/linear_algebra.rst  # 1 doctest failed
> ./sage -t --long --random-seed=0
> src/doc/en/developer/coding_in_other.rst  # 1 doctest failed
> --
> Total time for all tests: 36318.7 seconds
> cpu time: 10268.6 seconds
> cumulative wall time: 10657.8 seconds
> External software detected for doctesting:
> ffmpeg,graphviz,imagemagick,internet,latex,macaulay2,maple,octave,pandoc
> make: *** [Makefile:181: testalllong] Error 5
> ```
>
> Doctesting these files individually afterwards,
> each of them gave "All tests passed!"
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/CAEcArF3WNYJaEUZzAbCUpf_ZxHeZWNP366XE_0CYYfrBhJ-QPw%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAAWYfq1fgUOUgSm0YPmPSTh1iDt8ZM%3Db%3Dspv2AJbt%3DigxG5Tng%40mail.gmail.com.

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

2020-08-13 Thread Samuel Lelièvre 
Le mar. 11 août 2020 à 00:51, Volker Braun  a écrit :
>
> As always, you can get the latest beta version from the "develop"
> git branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html

Thanks! On Debian 10, success with `make`, and a few transient
timeouts and failures for `make testalllong`.

```
--
./sage -t --long --random-seed=0 src/sage/calculus/calculus.py  # Timed out
./sage -t --long --random-seed=0 src/sage/databases/findstat.py  # 17
doctests failed
./sage -t --long --random-seed=0 src/sage/databases/oeis.py  # 1 doctest failed
./sage -t --long --random-seed=0 src/sage/doctest/external.py  # Timed out
./sage -t --long --random-seed=0 src/sage/functions/gamma.py  # Timed out
./sage -t --long --random-seed=0 src/sage/interfaces/maple.py  # 15
doctests failed
./sage -t --long --random-seed=0 src/sage/interfaces/interface.py  # Timed out
./sage -t --long --random-seed=0 src/sage/interfaces/mathematica.py  # Timed out
./sage -t --long --random-seed=0 src/sage/interfaces/octave.py  # 3
doctests failed
./sage -t --long --random-seed=0 src/sage/interfaces/scilab.py  # Timed out
./sage -t --long --random-seed=0 src/sage/matrix/matrix1.pyx  # Timed out
./sage -t --long --random-seed=0 src/sage/misc/remote_file.py  # 1
doctest failed
./sage -t --long --random-seed=0 src/sage/misc/functional.py  # Timed out
./sage -t --long --random-seed=0
src/sage/modules/free_module_element.pyx  # Timed out
./sage -t --long --random-seed=0 src/sage/plot/plot.py  # 88 doctests failed
./sage -t --long --random-seed=0 src/sage/plot/graphics.py  # 63 doctests failed
./sage -t --long --random-seed=0 src/sage/symbolic/constants_c.pyx  # Timed out
./sage -t --long --random-seed=0 src/sage/symbolic/constants.py  # Timed out
./sage -t --long --random-seed=0 src/sage/symbolic/expression.pyx  # Timed out
./sage -t --long --random-seed=0
src/sage/symbolic/integration/integral.py  # Timed out
./sage -t --long --random-seed=0 src/sage/tests/benchmark.py  # Timed out
./sage -t --long --random-seed=0
src/doc/en/constructions/interface_issues.rst  # 1 doctest failed
./sage -t --long --random-seed=0
src/doc/en/constructions/linear_algebra.rst  # 1 doctest failed
./sage -t --long --random-seed=0
src/doc/en/developer/coding_in_other.rst  # 1 doctest failed
--
Total time for all tests: 36318.7 seconds
cpu time: 10268.6 seconds
cumulative wall time: 10657.8 seconds
External software detected for doctesting:
ffmpeg,graphviz,imagemagick,internet,latex,macaulay2,maple,octave,pandoc
make: *** [Makefile:181: testalllong] Error 5
```

Doctesting these files individually afterwards,
each of them gave "All tests passed!"

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAEcArF3WNYJaEUZzAbCUpf_ZxHeZWNP366XE_0CYYfrBhJ-QPw%40mail.gmail.com.

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

2020-08-11 Thread Matthias Köppe 
On Tuesday, August 11, 2020 at 3:12:38 PM UTC-7, Kenji Iohara wrote:
>
> I could compile Sage 9.2.beta 8 on Mac OS.10.15.6 and run sage. Quitting 
> sage has evoked no problem…
> But, for ptestlong, it has some errors. I don’t know whether this is 
> completely local porblem…
>

These doctest failures seem to come from locale issues. We have a ticket 
for these already - https://trac.sagemath.org/ticket/30053 - which needs 
help


-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/a6231f6c-0c6d-4448-97a5-a26cb641265eo%40googlegroups.com.