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

Release v2.26.1 #9016

Merged
merged 9 commits into from
Jan 29, 2025
Merged

Release v2.26.1 #9016

merged 9 commits into from
Jan 29, 2025

Conversation

cvat-bot[bot]
Copy link
Contributor

@cvat-bot cvat-bot bot commented Jan 29, 2025

Added

Changed

Removed

Fixed

cvat-bot bot and others added 9 commits January 28, 2025 07:01
Now that GHSA-wq36-mxf8-hv62 is fixed, it is actually safe to use
jsonpickle in this context.
Added a simple button to quickly copy frame name.
…default) (#9008)

This PR removes the `disableDistinctCachePerService` setting.
Previously this cache was used to cache chunks of data on storage, which
is not relevant now.
Currently only events need to be stored before being sent to Vector, and
this will always be cached for each service, so these settings are no
longer needed.

<!-- Raise an issue to propose your change
(https://github.com/cvat-ai/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://docs.cvat.ai/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. -->

### 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
- [ ] 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))

### License

- [x] I submit _my code changes_ under the same [MIT License](
https://github.com/cvat-ai/cvat/blob/develop/LICENSE) that covers the
project.
  Feel free to contact the maintainers if that's a concern.
Change location of events cache dir
@codecov-commenter
Copy link

Codecov Report

Attention: Patch coverage is 84.61538% with 2 lines in your changes missing coverage. Please review.

Project coverage is 73.39%. Comparing base (3513a64) to head (0a2ff48).
Report is 43 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #9016      +/-   ##
==========================================
- Coverage   73.40%   73.39%   -0.01%     
==========================================
  Files         415      416       +1     
  Lines       44192    44198       +6     
  Branches     3859     3860       +1     
==========================================
+ Hits        32437    32439       +2     
- Misses      11755    11759       +4     
Components Coverage Δ
cvat-ui 77.35% <66.66%> (-0.02%) ⬇️
cvat-server 70.09% <100.00%> (ø)

@cvat-bot cvat-bot bot merged commit 9c5ef99 into master Jan 29, 2025
31 checks passed
@cvat-bot cvat-bot bot deleted the release-2.26.1 branch January 29, 2025 18:42
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.

4 participants