Nushell core team meeting 2025-02-12

Attendees

  • Stefan
  • Piepmatz
  • Rose
  • Andy
  • Wind
  • Michael
  • Douglas
  • Antoine
  • Yash
  • Bahex
  • Renan - Cosineblast
  • Darren
  • Jack

Agenda

  • Point release?
    • Numeric overflow triggering panic in debug tests on 32-bit fixed by #15031
    • Panic on zero len slice fixed by #15062
    • other bug fixes without relevant breakage to collect
  • Behavior of background jobs on shell exit
  • Spring cleaning call to action / call for contributions
  • [ ]

Discussed Topics

Point release

Prompted by the Alpine build failure on 32-bit x86
Fix contributed for that by KAAthewisegit
A few panic-fixes we can put on the patch-release for the general userbase
Question about the Alpine build fail on aarch64 (seems to be in nu-plugin-polars) -> ask back and then decide if we wait for any fixes for that else ship a patch-release branch (stefan can take care of prepping the point release.)

Background job execution

  • Questions:
    • exit behavior
    • STDERR/STDOUT
  • Windows limitations
    • no fork mechanism
      • no way to cleanly launch a nushell internal process into a separate process.
      • externals can be lanched separately
    • No suspend via SIGSTOP
      • rose: maybe abuse SIGBRK
      • cosineblast: the signal would go to the child process if it has the terminal foreground, so possibly no way for us to cheat with SIGBRK
  • State of the PR
    • everything except ^Z/SIGSTP should work cross-platform on Windows
  • Future things to look into on UNIX
    • SIGCHLD
  • general consensus is to merge it when ready, play with it in nightlies. if we decide we should go for a different approach or we're otherwise not ready to include in a release, revert before next release

Spring cleaning

  • Test if issues are fixed, split issues containing multiple items into single issues
  • Make commands which claim to stream but actually don't just return a normal list
  • Make tests faster (plugin tests are slow?)
  • Go through list of "good first issues" and add/remove as needed
  • Go through github tags and remove old tags, be certain about what tags are clear
Select a repo