Singular

Singular commit 28d88317f5be18d83c49515617dfb0e38ae38600 added an error callback to NTL. If I understand that correctly, that callback completely halts the program.

That causes issues with the NTL usage in sage. Sage has its own error callback (used to catch errors and report them to the user). However with the newest singular, the program will just immediately halt whenever a NTL error occurs (even when using NTL directly).

Is that a bug?

Not a bug, just 2 parts of SAGE using the same error handler interface
- the last one wins.
We can move the initialization out of libSingular,
so that it is active only within Singular:
see
https://github.com/Singular/Sources/commit/502cf86d0bb2a96715be6764774b64a69c1ca34c

Thank you for the quick fix, that looks like it is exactly what we need!

Do you plan to make a release including this soon? Or do you know if it is possible to work around this until then?

Otherwise sage will have to continue using the old Singular version patch its Singular (backporting that commit). Because of that all the distributions packaging sage would either have to accept the error, stay at an older singular or patch their singular too.

Singular 4.1.1p3 will appear within the next week,
next relase (4.1.2?) probably in October.

Alright, that's perfect. Thank you for the quick fix!

singular-4.1.1p3 released