Editing Online Developer Meeting (2021-10-26)
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 11: | Line 11: | ||
* State of OpenBLAS compilation bug(?): [https://savannah.gnu.org/bugs/index.php?61246 bug #61246: matrix inversions give wrong results (inv, lu, mldivide)] | * State of OpenBLAS compilation bug(?): [https://savannah.gnu.org/bugs/index.php?61246 bug #61246: matrix inversions give wrong results (inv, lu, mldivide)] | ||
* <code>pkg test sparsersb</code> crashes Octave (only when installed to read-only directory?). Needs further investigation. | |||
* <code>pkg test sparsersb</code> crashes Octave (only when installed to read-only directory?). | |||
* Which version numbers to update in which files on (minor) release? (CITATION file?) | * Which version numbers to update in which files on (minor) release? (CITATION file?) | ||
* Update of merge date for Octave 7.x? | * Update of merge date for Octave 7.x? | ||
=== | === Fallback topic: <code>spawn</code> with <code>P_OVERLAY</code> works differently on POSIX and Windows === | ||
(Only if there is nothing else to talk about.) | |||
Markus' current understanding: | Markus' current understanding: | ||
Line 33: | Line 23: | ||
* On Windows, <code>spawn</code> with <code>P_OVERLAY</code> also replaces the current process. But each process has a distinct id on Windows. I.e., the new process gets a different process id from the original one. Another process (like a terminal) waiting for the original process id will resume once the '''original''' process terminates. (The same happens with <code>exec</code>.) That leads to issues when trying to use the <code>octave.exe</code> wrapper on Windows. | * On Windows, <code>spawn</code> with <code>P_OVERLAY</code> also replaces the current process. But each process has a distinct id on Windows. I.e., the new process gets a different process id from the original one. Another process (like a terminal) waiting for the original process id will resume once the '''original''' process terminates. (The same happens with <code>exec</code>.) That leads to issues when trying to use the <code>octave.exe</code> wrapper on Windows. | ||
* Could we use <code>spawn</code> with <code>P_WAIT</code> instead? IIUC, that would require passing the return code from the spawned process. What else? | * Could we use <code>spawn</code> with <code>P_WAIT</code> instead? IIUC, that would require passing the return code from the spawned process. What else? | ||
== Previous topics == | == Previous topics == |