fix(deps): update module github.com/cloudfoundry/gosigar to v1.3.102 #47
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.
This PR contains the following updates:
v1.2.0
->v1.3.102
Release Notes
cloudfoundry/gosigar (github.com/cloudfoundry/gosigar)
v1.3.102
Compare Source
v1.3.101
Compare Source
v1.3.100
Compare Source
v1.3.99
Compare Source
v1.3.98
Compare Source
v1.3.97
Compare Source
v1.3.96
Compare Source
v1.3.95
Compare Source
v1.3.94
Compare Source
v1.3.93
Compare Source
v1.3.92
Compare Source
v1.3.91
Compare Source
v1.3.90
Compare Source
v1.3.89
Compare Source
v1.3.88
Compare Source
v1.3.87
Compare Source
v1.3.86
Compare Source
v1.3.85
Compare Source
v1.3.84
Compare Source
v1.3.83
Compare Source
v1.3.82
Compare Source
v1.3.81
Compare Source
v1.3.80
Compare Source
v1.3.79
Compare Source
v1.3.78
Compare Source
v1.3.77
Compare Source
v1.3.76
Compare Source
v1.3.75
Compare Source
v1.3.74
Compare Source
v1.3.73
Compare Source
v1.3.72
Compare Source
v1.3.71
Compare Source
v1.3.70
Compare Source
v1.3.69
Compare Source
v1.3.68
Compare Source
v1.3.67
Compare Source
v1.3.66
Compare Source
v1.3.65
Compare Source
v1.3.64
Compare Source
v1.3.63
Compare Source
v1.3.62
Compare Source
v1.3.61
Compare Source
v1.3.60
Compare Source
v1.3.59
Compare Source
v1.3.58
Compare Source
v1.3.57
Compare Source
v1.3.56
Compare Source
v1.3.55
Compare Source
v1.3.54
Compare Source
v1.3.53
Compare Source
v1.3.52
Compare Source
v1.3.51
Compare Source
v1.3.50
Compare Source
v1.3.49
Compare Source
v1.3.48
Compare Source
v1.3.47
Compare Source
v1.3.46
Compare Source
v1.3.45
Compare Source
v1.3.44
Compare Source
v1.3.43
Compare Source
v1.3.42
Compare Source
v1.3.41
Compare Source
v1.3.40
Compare Source
v1.3.39
Compare Source
v1.3.38
Compare Source
v1.3.37
Compare Source
v1.3.36
Compare Source
v1.3.35
Compare Source
v1.3.34
Compare Source
v1.3.33
Compare Source
v1.3.32
Compare Source
v1.3.31
Compare Source
v1.3.30
Compare Source
v1.3.29
Compare Source
v1.3.28
Compare Source
v1.3.27
Compare Source
v1.3.26
Compare Source
v1.3.25
Compare Source
v1.3.24
Compare Source
v1.3.23
Compare Source
v1.3.22
Compare Source
v1.3.21
Compare Source
v1.3.20
Compare Source
v1.3.19
Compare Source
v1.3.18
Compare Source
v1.3.17
Compare Source
v1.3.16
Compare Source
v1.3.15
Compare Source
v1.3.14
Compare Source
v1.3.13
Compare Source
v1.3.12
Compare Source
v1.3.11
Compare Source
v1.3.10
Compare Source
v1.3.9
Compare Source
v1.3.8
Compare Source
v1.3.7
Compare Source
v1.3.6
Compare Source
What's Changed
New Contributors
Full Changelog: cloudfoundry/gosigar@v1.3.5...v1.3.6
v1.3.5
Compare Source
What's Changed
New Contributors
Full Changelog: cloudfoundry/gosigar@v1.3.4...v1.3.5
v1.3.4
: - Correctly report maximum memory when running in nested cgroups.Compare Source
Summary
This release contains PR #57. Reporting of maximum available memory for programs running in nested cgroups should now be correct.
For more information about the specifics of the issue, please consult this comment: #57 (comment).
Acknowledgements
Many thanks to @Nicholaswang for submitting PR #57 and bearing with us while we suggested changes to it.
v1.3.3
: - No longer panic when encountering cgroup controllers mounted in multiple locationsCompare Source
Fixes Issue #54. If a cgroup controller is mounted in multiple locations, the first mountpoint will be used rather than panicking.
Full Changelog: cloudfoundry/gosigar@v1.3.2...v1.3.3
v1.3.2
: - Export the newGetMemIgnoringCGroups
method properlyCompare Source
v1.3.1
: - Add GetMemIgnoringCGroups to FakeSigar for testingCompare Source
v1.3.0
: - GetMemIgnoringCGroupsCompare Source
v1.2.0 changed the behavior of the
GetMem
method to return cgroup-constrained memory information. This may not be the desired behavior for all use cases. v1.3.0 introduces a new methodGetMemIgnoringCGroups
that return system level memory information instead.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
To execute skipped test pipelines write comment
/ok-to-test
.This PR has been generated by MintMaker (powered by Renovate Bot).