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: update reva to fix status codes #8102

Merged
merged 3 commits into from
Jan 2, 2024
Merged

fix: update reva to fix status codes #8102

merged 3 commits into from
Jan 2, 2024

Conversation

micbar
Copy link
Contributor

@micbar micbar commented Jan 2, 2024

Description

Update reva to fix status codes.

Related Issue

Motivation and Context

How Has This Been Tested?

  • test environment:
  • test case 1:
  • test case 2:
  • ...

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Technical debt
  • Tests only (no source changes)

Checklist:

  • Code changes
  • Unit tests added
  • Acceptance tests added
  • Documentation ticket raised:

@saw-jan
Copy link
Member

saw-jan commented Jan 2, 2024

API tests require adjustment. I can have a look

Copy link

sonarcloud bot commented Jan 2, 2024

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@micbar micbar merged commit 853c34b into master Jan 2, 2024
4 checks passed
@delete-merged-branch delete-merged-branch bot deleted the update-reva branch January 2, 2024 13:21
ownclouders pushed a commit that referenced this pull request Jan 2, 2024
fix: update reva to fix status codes
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.

MOVE between Shares responds with 502
3 participants