Online Developer Meeting (2022-02-22): Difference between revisions

Jump to navigation Jump to search

Online Developer Meeting (2022-02-22) (view source)

Revision as of 07:58, 21 February 2022

2,173 bytes added ,  21 February 2022
Add some topics for upcoming meeting
(Create page.)
 
(Add some topics for upcoming meeting)
Line 6: Line 6:
* Meet and greet 5 minutes before meeting (audio testing).
* Meet and greet 5 minutes before meeting (audio testing).


=== Release process of Octave 7.1 ===
* Blocking issues: 9 bugs targeting 7.0.90, 3 marked as "ready for test" (see [https://octave.space/savannah/# Savannah overview on octave.space])
* Good progress on some of the blocking issues by jwe. Most important remaining ones:
** bug {{bug|61788}}: arrays of type int16 contain wrong numbers
*** The <code>:</code>-operator will probably be changed to return an array (instead of a range object) before Octave 7. Not started yet.
** bug {{bug|61813}}: memory management bug when calling MEX that returns an output]
*** @jwe provided an initial changeset. That will also revert to copying from the .mex interface unless Octave is compiled with C++17 pmr.
** bug {{bug|61821}}: segfault using tree_parameter_list in oct file]
*** Lower priority, only 32-bit (only on Windows?). Probably not a blocker.
** bug {{bug|61898}}: subsref: Error when field syntax is used on non-scalar @class object
*** Not a bug in Octave core. Recent changes to output argument validation uncovered an issue in interval package.
** Similar bug {{bug|61843}}: Regression with subscripted assignments with arrays of objects
*** Older regression.


=== Minimum Qt5 version for Octave 8? ===
* See [https://octave.discourse.group/t/qt5-15-already-unsupported-upstream-except-commercial-license/737/15 Qt5.15 already unsupported upstream (except commercial license)?]


== Previous topics ==
== Previous topics ==
Line 15: Line 32:
* Blocking issues: 9 bugs targeting 7.0.90 (see [https://octave.space/savannah/# Savannah overview on octave.space])
* Blocking issues: 9 bugs targeting 7.0.90 (see [https://octave.space/savannah/# Savannah overview on octave.space])
* Most important ones (in no particular order):
* Most important ones (in no particular order):
** bug {{bug|61788}}: arrays of type int16 contain wrong numbers]
** bug {{bug|61788}}: arrays of type int16 contain wrong numbers
*** Will probably be reverted before Octave 7.
*** The <code>:</code>-operator will probably be changed to return an array (instead of a range object) before Octave 7.
** bug {{bug|61813}}: memory management bug when calling MEX that returns an output]
** bug {{bug|61813}}: memory management bug when calling MEX that returns an output
*** Issue if Octave is compiled with C++17, while the mex file not. @jwe checks on this.
*** Probably caused by changes for more efficient data interface for .mex files.  @jwe will check this.
*** maybe also: <code>malloc</code>-<code>delete[]</code> combination in the .mex interface
** Possible issues if Octave is compiled with C++17 (<code>--enable-pmr-polymorphic-allocator</code>), while .oct files are not.
** bug {{bug|61821}}: segfault using tree_parameter_list in oct file]
*** Maybe change the API string if Octave is configured with polymorphic allocators?
*** Lower priority, only conditionally reproducible.
*** Leave that option in. But disable it by default. (That is already the current state.)
** bug {{bug|61898}}: subsref: Error when field syntax is used on non-scalar @class object]
** <code>malloc</code>-<code>delete[]</code> combination in the .mex interface
*** Needs reproducible example without interval package. Similar bug {{bug|61843}} reported.   
*** No decision made. Maybe leave as is?
* A few package releases with fixes for Octave 7 were pushed to mxe default, e.g. https://hg.octave.org/mxe-octave/rev/d601436d29f2 (ga, control, communications)
** bug {{bug|61821}}: segfault using tree_parameter_list in oct file
** Should those changes be applied to the "release" branch?  -YES.
*** Check if we are doing something wrong for 32bit. Probably not a blocker.
** bug {{bug|61898}}: subsref: Error when field syntax is used on non-scalar @class object
*** Try finding a minimal reproducer (without interval package). Similar bug {{bug|61843}} reported.   
* A few package releases with fixes for Octave 7 were pushed to the default branch of MXE Octave, e.g. https://hg.octave.org/mxe-octave/rev/d601436d29f2 (ga, control, communications)
** Should those changes be grafted to the "release" branch?  -YES.
* Revisit load path caching: https://octave.discourse.group/t/rfc-remove-faulty-load-path-caching/2136
* Revisit load path caching: https://octave.discourse.group/t/rfc-remove-faulty-load-path-caching/2136
** Improving the caching strategy is the way to go.
** Improving the caching strategy is the way to go (see e.g. bug {{bug|54636}}).
** Long-term: A complete overhaul of the load path caching implementation is probably necessary.


=== C++17 features in Octave API? ===
=== C++17 features in Octave API? ===
Line 36: Line 58:
* Should we announce that possible requirement for some time in the future with the release of Octave 7?
* Should we announce that possible requirement for some time in the future with the release of Octave 7?
* See also: [https://octave.discourse.group/t/should-octave-switch-to-c-17-if-so-when/2114 Should Octave switch to C++17? If so, when?] on Discourse.
* See also: [https://octave.discourse.group/t/should-octave-switch-to-c-17-if-so-when/2114 Should Octave switch to C++17? If so, when?] on Discourse.
* We'll start an experiment by enabling polymorphic allocators for default Octave on the default branch of MXE Octave. We'll evaluate if the necessary changes to dependent packages are trivial.


=== GSOC 2022 opening soon ===
=== GSOC 2022 opening soon ===
Retrieved from "https://wiki.octave.org/Special:MobileDiff/14205"

Navigation menu