Alan King

I think we determined that that's going to be hard because we would have to configure remote servers from inside the test and/or read from a remote log (see https://github.com/irods/irods/issues/4164).

Got verbal approval, so let's go ahead and add #'s.

No, just this one. We can address the other PRs in turn.

If you feel that they must all be merged together, then hold off on #'s until all of them are approved.

I created #5744 to address the stacktrace. That's not acceptable. We will continue to look into the other issues.

Right, I don't know that there is a lot we can do about the correctness of the result apart from operation locking. Solving the "database race" we have discussed previously...

Related to this comment: https://github.com/irods/irods/issues/6879

While investigating this and #6479, I observed a crash in the agent servicing an `iput` which targeted a misconfigured S3 resource. Note: The file specified for `S3_AUTH_FILE` does not exist,...

I have confirmed a fix on the main branch which requires a change to the S3 resource plugin as well as `replica_close`, as described by OP. In addition to the...

I have now observed this on a test run against 4.3.0 as released. Trying on 4-2-stable shortly