[noissue]: Update djangorestframework requirement from ~=3.12.4 to ~=3.14.0 #101
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[noissue]
Redmine Query: https://pulp.plan.io/issues?set_filter=1&status_id=*&issue_id=8823,8876,8883,8897,8947,8881,8801,8501,8800,8805,8729,8487,8946,8975,8658,8891,8869,8480,8774,8949,8827,8637,8868,8867,8980,8844,6837,8670,8708,8948,8926,8803,8930,8821 Redmine Milestone: https://pulp.plan.io/versions/218.json [noissue]
[noissue]
[noissue]
The change pins towncrier to 19.9.0 and also adds an optional parameter to the release workflow. The optional 'before_script' parameter allows custom bash code to be run before script.sh is run. This is useful for resolving docs issues after a release. [noissue]
This patch clearly defines the exported_resources as a list of URI strings. The implementation for the ExportedResourceSerializer is shared with CreatedResource serializer. They now both inherit from a new RelatedResourceField. backports: #9008 https://pulp.plan.io/issues/9008 fixes #9025 (cherry picked from commit f52ba80)
backports: #9003 https://pulp.plan.io/issues/9003 fixes #9015 (cherry picked from commit e4b1724)
[noissue]
Redmine Query: https://pulp.plan.io/issues?set_filter=1&status_id=*&issue_id=9015,9025 Redmine Milestone: https://pulp.plan.io/versions/257.json [noissue]
[noissue]
backports: #9024 https://pulp.plan.io/issues/9024 fixes #9068 (cherry picked from commit 0c9541d)
backports: #9039 https://pulp.plan.io/issues/9039 fixes #9059 (cherry picked from commit 2cc9804)
backports #8954 fixes #9058 (cherry picked from commit 3bc707a)
This unskips the `Range` header and adds support for it to the content app. backports #8865 fixes #9057 (cherry picked from commit df2c8f1)
backports: #9074 fixes #9077 (cherry picked from commit ca0ef8f)
If Redis goes down then its persisted data can get out of sync with Pulp, because cache invalidation events cannot occur. We should mitigate the impact by letting cache entries expire after a shorter period of time. backports: #8996 https://pulp.plan.io/issues/8996 fixes #9063 (cherry picked from commit 017b0b1)
[noissue]
Redmine Query: https://pulp.plan.io/issues?set_filter=1&status_id=*&issue_id=9077,9059,9068,9057,9058,9063 Redmine Milestone: https://pulp.plan.io/versions/259.json [noissue]
[noissue]
[noissue]
When hitting ctrl-c twice, workers should also kill their supervised tasks. And shut them down. backports #8986 https://pulp.plan.io/issues/8986 fixes #9086 (cherry picked from commit 80d7d6d)
Before this change, it was not possible to determine why did the synchronization fail when a user provided a seemingly valid URL. This commit also adds more relevant information to the error message.
Having set `ALLOWED_EXPORT_PATHS` to `["/tmp", "/home/vagrant/test"]`, the following error messages are shown:
```
$ pulp file remote create --name test --url file://error/vagrant/test/centos-7/PULP_MANIFEST
Error: {"url":["The path 'error/vagrant/test/centos-7/PULP_MANIFEST' needs to be an absolute pathname."]}
$ pulp file remote create --name test --url file:///error/vagrant/test/centos-7/PULP_MANIFEST
Error: {"url":["The path '/error/vagrant/test/centos-7/PULP_MANIFEST' does not start with any of the allowed import paths"]}
```
backports #9080
fixes #9083
(cherry picked from commit d8cba5a)
Redis is only used when cache is enabled or RQ tasking is used. In other cases, the connection is not needed. We've changed the Foreman installer to only install Redis if needed, just to stop wasting resources[1]. However, this leads to warnings. This PR changes the status view to only include Redis if it's used. [1]: theforeman/puppet-pulpcore@7a5543b backports #9070 https://pulp.plan.io/issues/9070 fixes #9085 (cherry picked from commit 8ab8afb)
backports #8779 fixes #9116 (cherry picked from commit 0cfaa8e)
As of this commit, content app is no longer storing temporary files in the /var/run/ directory. The temporary files were created during on-demand downloading and were not removed until, e.g., restarting pulp services. backports #9000 fixes #9110 (cherry picked from commit f8bd7f8)
Before this commit, the condition that checks whether pulp's temporary files are stored within /var/lib/pulp was never met because it looked for files starting with /var/lib/pulp/media (MEDIA_ROOT). MEDIA_ROOT is however no longer pointing to /var/lib/pulp. backports #8295 fixes #9103 (cherry picked from commit fbe2d7f)
[noissue]
[noissue]
Redmine Query: https://pulp.plan.io/issues?set_filter=1&status_id=*&issue_id=9244,9282,9261,9268,9264,9273,9265 Redmine Milestone: https://pulp.plan.io/versions/278.json [noissue]
[noissue]
Instead perform a simple xor on the first and second half of the task uuid. backports #9249 fixes #9288 (cherry picked from commit 1d77e5c)
aiohttp automatically enflates gzipped responses. Pulp clients always receive uncompressed responses when requesting on_demand content. backports: #9213 fixes #9325 (cherry picked from commit 7e0a79e)
For some strange reason some Openshift environments do not like the runtime import the worker entrypoint used. Moving it to the top where it belongs anyway resolves the problem. backports #9338 fixes #9339 (cherry picked from commit 022d2e3)
[noissue]
Redmine Query: https://pulp.plan.io/issues?set_filter=1&status_id=*&issue_id=9288,9325,9339 Redmine Milestone: https://pulp.plan.io/versions/281.json [noissue]
[noissue]
backports #9266. closes: #9401 (cherry picked from commit 4023fce)
backports #9395. closes: #9400 (cherrypicked from commit 489156e)
backports #9427. closes: #9440 [nocoverage] (cherry picked from commit 6e18f2e)
All workers that are considered offline will be removed from the database periodically. backports #8931 fixes #9462 (cherry picked from commit 5bbf959)
backports: #9427 fixes #9453 (cherry picked from commit 6fb9109)
Forcing deadlocks requires a lot of time and pulpcore-workers running. There is therefore no specific CI test for this, but there is a reproducer script that will force deadlocks to happen (and show that they're fixed) here: https://github.com/ggainey/pulp_startup/blob/main/8750_deadlocks/file_repro.sh backports #8750 fixes #9379 (cherry picked from commit 6af3519)
[noissue]
Redmine Query: https://pulp.plan.io/issues?set_filter=1&status_id=*&issue_id=9462,9401,9440,9379,9400,9453,9445 Redmine Milestone: https://pulp.plan.io/versions/302.json [noissue]
[noissue]
closes #9491 backports #9301 (cherry picked from commit 8a1db3b)
[noissue]
Redmine Query: https://pulp.plan.io/issues?set_filter=1&status_id=*&issue_id=9491 Redmine Milestone: https://pulp.plan.io/versions/313.json [noissue]
[noissue]
SimpleTestCase does not allow database access. [noissue]
[noissue]
Updates the requirements on [djangorestframework](https://github.com/encode/django-rest-framework) to permit the latest version. - [Release notes](https://github.com/encode/django-rest-framework/releases) - [Commits](encode/django-rest-framework@3.12.4...3.14.0) --- updated-dependencies: - dependency-name: djangorestframework dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the requirements on djangorestframework to permit the latest version.
Commits
2da473cAdd 3.14 announcement to the docs58e0a69Update setup.py to drop Django 2.2 and update release notes (#8666)11bfda9both statement have dupplicate bodies (#8633)058424cdocs: delete duplicate explanation (#8641)eb88dfcAdd --api-version CLI option to generateschema (#8663)f34f156Remove old deprecation classes for 3.14 release (#8664)c6cafc9Update release-notes.mdf8b3f38Update supported versions for 3.14 release (#8662)b658915Version 3.14.0 proposal (#8599)51f1affRevert 8552 (#8661)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)