-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[ws-daemon] Currectly use limit writer #4969
Conversation
@csweichel: GitHub didn't allow me to request PR reviews from the following users: this, has, potentially, config, breaking, changes. Note that only gitpod-io members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/approve |
/auto-cc |
/lgtm |
LGTM label has been added. Git tree hash: 22a765a0947aef31d876a23bf914539f66e6ffc3
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aledbf, csweichel Associated issue: #4961 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold @meysholdt should be aware of this change |
/hold cancel |
Codecov Report
@@ Coverage Diff @@
## main #4969 +/- ##
=========================================
+ Coverage 0 31.09% +31.09%
=========================================
Files 0 71 +71
Lines 0 14746 +14746
=========================================
+ Hits 0 4585 +4585
- Misses 0 9744 +9744
- Partials 0 417 +417
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
This PR enables the use of the
limitWriter
in ws-daemon. While previously existing, it was not used (anymore?). In the same vein, I've removed the storage-specific maximum backup configuration. Instead, we're now using a single size to determine how large a workspace can be:gitpod/components/ws-daemon/pkg/content/config.go
Line 32 in 40f913c
/cc @meysholdt
this has potentially config breaking changes
fixes #4961