feat: Add a sanity check layer to detect if services return unexpected responses

[amunra]

Describe the bug

There seems to be an incompatibility between OpenDAL and s3s-fs.
I've raised the issue here with s3s-fs s3s-project/s3s#350

The TL;DR is that when writing data and then calling op.list("/").await, the OpenDAL client will freeze.

This very well might be because of an invalid response from the server, but either way, the client shouldn't hang (I think, unless I'm wrong).

Steps to Reproduce

See s3s-project/s3s#350 for test-case repro.

Expected Behavior

List contents without hanging.

Additional Context

No response

Are you willing to submit a PR to fix this bug?

• Yes, I would like to submit a PR.

[Xuanwo]

Hi, thank you for using OpenDAL. I see this issue has been fixed on the s3s side at s3s-project/s3s#351. What is the expection for this issue?

[Xuanwo]

Oh, I see.

This very well might be because of an invalid response from the server, but either way, the client shouldn't hang (I think, unless I'm wrong).

It’s possible to add a sanity check in OpenDAL to detect if services return unexpected responses, for example, by verifying that the same key was received. This could serve as a separate layer.

[Xuanwo]

I will rename this issue to better reflect it's intention now.