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

Fix response status if not found (#39) #40

Merged
merged 4 commits into from
Jun 29, 2020
Merged

Conversation

yichen88
Copy link
Contributor

@yichen88 yichen88 commented Mar 23, 2020

Signed-off-by: yichen88 [email protected]

Please check if the PR fulfills these requirements (please use '[x]' to check the checkboxes, or submit the PR and then click the checkboxes)

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

Does this PR already have an issue describing the problem ? If so, link to this issue using '#XXX' and skip the rest
#39

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change or deprecate an API? If yes, check the following:

  • The Breaking Change or Deprecated label has been added
  • The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)

Other information:

(if any of the questions/checkboxes don't apply, please delete them entirely)

@yichen88 yichen88 requested a review from jonenst March 23, 2020 12:55
if (status == Response.Status.OK) {
return Optional.of(readEntityAndLog(response, entityType));
} else if (status == Response.Status.NO_CONTENT) {
if (status == Response.Status.NO_CONTENT || status == Response.Status.NOT_FOUND) {
LOGGER.trace(" --> null");
return Optional.empty();
Copy link
Contributor

Choose a reason for hiding this comment

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

Why do you remove the INTERNAL_SERVER_ERROR case ?

Copy link
Contributor

Choose a reason for hiding this comment

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

and the UnexpectedResponse case ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

these cases are still checked in readEntityIfOk().

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah yes sorry, didn't see it.

if (status == Response.Status.OK) {
return Optional.of(readEntityAndLog(response, entityType));
} else if (status == Response.Status.NO_CONTENT) {
if (status == Response.Status.NO_CONTENT || status == Response.Status.NOT_FOUND) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe add a comment that the NO_CONTENT is for backwards compatibility with afs-server < version XX

@sonarcloud
Copy link

sonarcloud bot commented Mar 27, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@mathbagu
Copy link
Contributor

@yichen88 Could you please solve the DCO
@jonenst Could you complete the review please?

Signed-off-by: yichen88 <[email protected]>
@yichen88 yichen88 force-pushed the fix_not_found_api branch from eeb6745 to 62f3203 Compare June 16, 2020 14:15
@jonenst
Copy link
Contributor

jonenst commented Jun 23, 2020

Thanks, sorry for the delay !

@sonarcloud
Copy link

sonarcloud bot commented Jun 29, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

warning The version of Java (1.8.0_252) you have used to run this analysis is deprecated and we will stop accepting it from October 2020. Please update to at least Java 11.
Read more here

@mathbagu mathbagu merged commit f47a619 into master Jun 29, 2020
@mathbagu mathbagu deleted the fix_not_found_api branch June 29, 2020 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants