Open rhegner opened 4 months ago
Moving it to relevant project
Looking into it...
Reproduced it and working on it.
PutObjectAsync
and BucketExistsAsync
also seem to ignore errors in 6.0.3 (6.0.1 is fine)
@codewing Thank you for the info.
I think PR #1141 has fixed several issues including this one. I appreciate if you could test and verify the fix. Please let me know about your test results and findings.
@ebozduman I did not run my tests yet, but just from looking at the code I still have some concerns regarding error handling, see https://github.com/minio/minio-dotnet/pull/1141#issuecomment-2250123299
@rhegner
I agree the error handling is complex and problematic and its maintenance and testing is cumbersome. Until it is redesigned though, we have to support it IMHO, or until mngmt makes a decision about it.
I appreciate it if you could test the fix in your environment and let us know an of course open up a new issue if required.
What about the problem? Is there anything else going on here?
@tinohager
There is some work that has been done and completed to fix the issue, but testing the fix and tuning it up for all possible scenarios requires considerable amount of time. Unfortunately, sometimes a higher priority task might slow down the progress of this issue and the reviewers are expected to be extremely thorough when the fix is ready.
Maybe you should at least mark the package in Nuget/Github that there are problems with the current version.
Pin Issue
Expected Behavior
When calling functions like
StatObjectAsync
orGetObjectAsync
, the SDK should throw exceptions if connection to Minio could not be established.Current Behavior
No exceptions are thrown in SDK v6.0.2 and v6.0.3.
This is especially bad in this example where we rely on proper exception handling to detect if an object exists:
The code returns true even though the Minio server could not even be reached.
Steps to Reproduce (for bugs)
This is my testbed:
Regression
Error handling is broken (in different ways) since v6.0.1.
Your Environment
Minio 6.0.3