With the new issue reporting mechanism in place (PR #2605), the old TraceEvent cache based implementation specifically for trace file open failure can be removed.

I have noticed a small error in the documentation around S3 configurations:
https://docs.delta.io/latest/delta-storage.html#amazon-s3

On the read part, it should be load and not save:
spark.read.format("delta").load("s3a://<your-s3-bucket>/<path>/<to>/<delta-table>")

Also, I have successfully tested Delta 0.5.0 with on-premise S3 - https://min.io
There were some quirks around the

Currently libfpta uses /dev/shm or /tmp for temporary databases while testing.
This should be isolated on per-user basis to avoid conflicts.

Workaround:

• don't start more that one test suite simultaneously.
• manually delete all *.fpta and *.fpta-lck files inside /dev/shm or /tmp.

Satisfies and 3.6.1 and 3.7.1