Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warnings #806

Merged
merged 11 commits into from
Aug 3, 2023
Merged

Warnings #806

merged 11 commits into from
Aug 3, 2023

Conversation

martijn00
Copy link
Contributor

@ebozduman another round of warnings.

@martijn00
Copy link
Contributor Author

@ebozduman can you run again?

@martijn00
Copy link
Contributor Author

@ebozduman trying to track down the test issues I find it sometimes difficult to see where they come from now they run in parallel. Do you have any suggestions?

I tried this:

        await Utils.RunInParallel(functionalTestTasks, async (task, _) => {
            try
            {
                await task.ConfigureAwait(false);
            }
            catch (Exception)
            {
                throw task.Exception;
            }
        })
            .ConfigureAwait(false);

Which does help a bit to see the inner exception. What do you think?

@ebozduman
Copy link
Collaborator

@martijn00

Great idea!
I'll also use it.

@martijn00
Copy link
Contributor Author

@ebozduman can you run this one again?

@ebozduman
Copy link
Collaborator

...sometimes difficult to see where they come from now they run in parallel. Do you have any suggestions?

I forgot to answer your previous question.

I used the following cancellation token related change at the end of the ExecuteTaskCoreAsync function to see if the test stops because a cancellation was requested.

        catch (OperationCanceledException ex)
        {
            if (ex.CancellationToken.IsCancellationRequested )
            {
                Console.WriteLine($"\n\n\nYes, Cancellation Requested\n\n\n");
            }
            throw;
        }
        catch (Exception e)
        {
            responseResult?.Dispose();
            responseResult = new ResponseResult(request, e);
        }

        HandleIfErrorResponse(responseResult, errorHandlers, startTime);
        return responseResult;
    }

@ebozduman
Copy link
Collaborator

@martijn00

I guess you need to run dotnet regitlint.

!!!! Process Aborted !!!!
The following files do not match .editorconfig:
 * Minio/Credentials/AssumeRoleProvider.cs
 * Minio/DataModel/Args/PutObjectPartArgs.cs
 * Minio/DataModel/Tags/Tagging.cs
 * Minio/ResponseResult.cs
Error: Process completed with exit code 1.

@martijn00
Copy link
Contributor Author

@ebozduman done. can you run again?

@martijn00
Copy link
Contributor Author

@ebozduman all green here! Can you merge?

@ebozduman
Copy link
Collaborator

currently reviewing.
As soon as I am done, I'll merge the PR

ebozduman

This comment was marked as duplicate.

@ebozduman ebozduman dismissed their stale review August 3, 2023 23:52

unintended request

Copy link
Collaborator

@ebozduman ebozduman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ebozduman ebozduman merged commit e7550db into minio:master Aug 3, 2023
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants