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 export of resources to cloud storage #7317

Merged
merged 12 commits into from
Jan 15, 2024

Conversation

Marishka17
Copy link
Contributor

@Marishka17 Marishka17 commented Jan 4, 2024

Motivation and context

In the previous implementation logic to upload created files to cloud storage was in the code that processes requests. This resulted in responses with 504 status when uploading a file took longer than the request timeout. This PR fixes the described problem.

How has this been tested?

Checklist

  • I submit my changes into the develop branch
  • I have created a changelog fragment
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • I have linked related issues (see GitHub docs)
  • I have increased versions of npm packages if it is necessary
    (cvat-canvas,
    cvat-core,
    cvat-data and
    cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.

@Marishka17 Marishka17 requested a review from SpecLad as a code owner January 5, 2024 12:11
@Marishka17 Marishka17 requested a review from nmanovic as a code owner January 8, 2024 22:26
Copy link

codecov bot commented Jan 8, 2024

Codecov Report

Merging #7317 (2e8764f) into develop (a684c0c) will increase coverage by 0.01%.
Report is 1 commits behind head on develop.
The diff coverage is 87.77%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #7317      +/-   ##
===========================================
+ Coverage    82.94%   82.95%   +0.01%     
===========================================
  Files          373      373              
  Lines        39600    39615      +15     
  Branches      3704     3701       -3     
===========================================
+ Hits         32847    32864      +17     
+ Misses        6753     6751       -2     
Components Coverage Δ
cvat-ui 78.41% <100.00%> (+<0.01%) ⬆️
cvat-server 87.12% <86.90%> (+0.01%) ⬆️

@Marishka17 Marishka17 changed the title [Do not merge] Fix export of resources to cloud storage Fix export of resources to cloud storage Jan 9, 2024
@Marishka17 Marishka17 changed the title Fix export of resources to cloud storage [WIP] Fix export of resources to cloud storage Jan 11, 2024
@Marishka17 Marishka17 changed the title [WIP] Fix export of resources to cloud storage Fix export of resources to cloud storage Jan 11, 2024
@azhavoro azhavoro merged commit 906260c into develop Jan 15, 2024
33 checks passed
@azhavoro azhavoro deleted the mk/fix_export_to_cloud_storage branch January 15, 2024 13:04
bsekachev pushed a commit that referenced this pull request Jan 17, 2024
<!-- Raise an issue to propose your change
(https://github.com/opencv/cvat/issues).
It helps to avoid duplication of efforts from multiple independent
contributors.
Discuss your ideas with maintainers to be sure that changes will be
approved and merged.
Read the [Contribution
guide](https://opencv.github.io/cvat/docs/contributing/). -->

<!-- Provide a general summary of your changes in the Title above -->

### Motivation and context
<!-- Why is this change required? What problem does it solve? If it
fixes an open
issue, please link to the issue here. Describe your changes in detail,
add
screenshots. -->
In the previous implementation logic to upload created files to cloud
storage was in the code that processes requests. This resulted in
responses with 504 status when uploading a file took longer than the
request timeout. This PR fixes the described problem.
### How has this been tested?
<!-- Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to
see how your change affects other areas of the code, etc. -->

### Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply.
If an item isn't applicable for some reason, then ~~explicitly
strikethrough~~ the whole
line. If you don't do that, GitHub will show incorrect progress for the
pull request.
If you're unsure about any of these, don't hesitate to ask. We're here
to help! -->
- [x] I submit my changes into the `develop` branch
- [x] I have created a changelog fragment <!-- see top comment in
CHANGELOG.md -->
- [ ] I have updated the documentation accordingly
- [ ] I have added tests to cover my changes
- [ ] I have linked related issues (see [GitHub docs](

https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))
- [x] I have increased versions of npm packages if it is necessary

([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning),

[cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning),

[cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning)
and

[cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))

### License

- [x] I submit _my code changes_ under the same [MIT License](
https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the
project.
  Feel free to contact the maintainers if that's a concern.
@cvat-bot cvat-bot bot mentioned this pull request Jan 18, 2024
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