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

Service Bus : fix for issues 5058 and 5055 #6911

Merged
merged 10 commits into from
Aug 20, 2018

Conversation

v-Ajnava
Copy link
Member

Description

Checklist

markcowl
markcowl previously approved these changes Aug 16, 2018
@v-Ajnava
Copy link
Member Author

v-Ajnava commented Aug 16, 2018

@MiYanni , the CI failed with message 'Starting test execution, please wait... The job exceeded the maximum time limit for jobs, and has been terminated.' can you please restart the CI.

@MiYanni
Copy link
Contributor

MiYanni commented Aug 16, 2018

@v-Ajnava You'll need to merge in latest preview into your fork. We've removed some tests from NetCore so the Travis CI process can pass. Right now, I don't think you'll have those changes.

@MiYanni
Copy link
Contributor

MiYanni commented Aug 16, 2018

@v-Ajnava It seems I'm incorrect. Your branch is already up to date with preview. Let me investigate.

@MiYanni
Copy link
Contributor

MiYanni commented Aug 16, 2018

@v-Ajnava I got it working. The issue was not related to your PR.

@v-Ajnava
Copy link
Member Author

@MiYanni Thanks !

Copy link
Member

@cormacpayne cormacpayne left a comment

Choose a reason for hiding this comment

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

@v-Ajnava one comment, otherwise LGTM

public static ErrorRecord WriteErrorforBadrequest(ErrorResponseException ex)
{
ErrorResponseContent errorExtract = new ErrorResponseContent();
errorExtract = JsonConvert.DeserializeObject<ErrorResponseContent>(ex.Response.Content);
Copy link
Member

Choose a reason for hiding this comment

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

@v-Ajnava can we do some null-checking in this function to ensure that ex, ex.Response, and ex.Response.Content have a value?

Copy link
Member Author

Choose a reason for hiding this comment

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

resolved

v-ajnava added 3 commits August 17, 2018 13:05

public static ErrorRecord WriteErrorforBadrequest(ErrorResponseException ex)
{
if (ex != null && !string.IsNullOrEmpty(ex.Response.Content))
Copy link
Member

Choose a reason for hiding this comment

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

Is Response guaranteed to be non-null?

Copy link
Member Author

Choose a reason for hiding this comment

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

yes, response will not be null

@markcowl markcowl dismissed cormacpayne’s stale review August 20, 2018 05:22

all comments answered

@markcowl markcowl merged commit 5c259d3 into Azure:preview Aug 20, 2018
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.

6 participants