Terrell Russell

Is there anything we can do to fix the original invalid address situation? Can we reproduce it today in 4.2.11+? We've already moved the REI context information into the database...

We have only been testing up to this point with the database versions that ship with the tested operating systems. We're changing that with our new CI and plan to...

we know postgres12 is now a problem with the current unixodbc (https://github.com/irods/irods/issues/5325)

good to squash and swap issue number?

last line of last commit message... "allwos us to sidestep" -> "allows us to sidestep"

Makes a lot of sense. Good insight.

Just for posterity... ``` $ ierror 23000 irods error: -23000 SYS_BAD_FILE_DESCRIPTOR ``` We should eyeball whether this has been touched/fixed since 4.2.8 (a lot has moved since then).

Ah, @tedgin... can you run your test script in a 4.2.11 server? My own attempt seems to work for me... ``` $ cat 6469.sh set -x -e truncate -s35M 35Mfile...

only on Debian11?

Hrm, pretty sure we tested that... Thanks!