Online Developer Meeting (2025-01-28)
Jump to navigation
Jump to search
- Date: Tuesday, January 28, 2025 @ 18:00 UTC Convert timezones here!
- Location: https://meet.jit.si/octave-dev
Today's topics
- Another Octave 9.x release? (Issue with load path update on Windows)
- Spam on Wiki: Discourse thread
- Should we consolidate the number of automated pulls from savannah via HTTPS? See also support ticket for Savannah admins.
- buildbot.octave.org: every 5 minutes (for stable and default branches) and for each triggered build
- nightly.octave.org: every 10 minutes (for stable branch) and once per day if a build is triggered.
- synchronization to GitHub repository: every 5(?) minutes (for stable, default, and bytecode-interpreter branches)
- Apple Accelerate and single precision floating point numbers. See also the Discourse thread.
- load path update with files in "execution stack". See also bug #66659: Octave crashes with SIGSEGV when debugging class methods
- GSOC 2025:
- confirm interest and/or support intent?
- several early inquiries - Worth it to update/augment/create 'welcome' info?
- GSOC page list probably stale, other project list likely as well. We have a number of big ideas with full range of progress from 0 to ??.
- Can any _portions_ be turned into summer sized projects to kickstart activity? (Qt dev? GUI? Aspects of Classdef? HDF5, etc?)
- We can always reject any unsound proposals, but history seems to suggest we'll only get solid applicants for proposed ideas.
- Based on 2024 issues, establish/publish a 'no selection if no pre-proposal communication' policy?
- How to publish package on Octave Forge? See bug #66705: vrml package does not install
Previous topics
- Release of Octave 9.3.0?
- Rik and Markus helped jwe make the release files.
- There was a problem with
asin
on Windows (https://octave.discourse.group/t/failing-test-for-mxe-octave-after-crossbuilding-on-fedora-41/6026/80). - The release should be done by the time of the meeting. This topic is here as a reminder (as if one is needed) to discuss the release process and the
asin
bug.
- Digital Ocean server - load and disc space
- load and used memory was on reasonable levels during the time available on the history provided by Digital Ocean
- disc usage is high
- jwe will increase the size of the extra partition from 5 GB to 10 GB (pricing approx. 1c US-ct per GB per month)
- Buildbot availability
- The memory issue of one of the machines running the buildbot workers has been resolved (defective memory bar has been replaced)
- The SSDs have been replaced with larger ones. When copying files from the old to the new SSDs, already some read errors. (The SSDs might have needed to be replaced soon in any case.)
- jwe will look into setting up an autostart of the buildbot worker for nightly.octave.org on startup. That worker is running in a docker container.
- Timeline or blockers for Octave 10?
- Issue with new files not being detected immediately after saving in built-in editor. Might be possible to resolve by rehashing the load_path after a new file was saved.
- Rik would like to push changes for
mod
,rem
, andqr
for Octave 10
- "Code sprint" for new terminal widget?
- Likely not in time for Octave 10
- Old problem - windows file timestamps - (bug #31080)
- See above (blockers for Octave 10)
- jwe will try to establish weekly "office hours" for developers or users with questions to Octave internals are invited to call in.
See also
- Next meeting: Online Developer Meeting (2025-02-25)
- Prev meeting: Online Developer Meeting (2024-12-17)