-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Patch release 2.7.3 #21214
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
Merged
Merged
Patch release 2.7.3 #21214
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
Limit cgroup discovery to a maximum number of entries and log a warning if exceeded (cherry picked from commit 211b482)
(cherry picked from commit 88983f0)
Skip adding Sentry breadcrumb during shutdown timeout to prevent crashes (cherry picked from commit cca892a)
…ng (netdata#21155) (cherry picked from commit d22056f)
(cherry picked from commit feefb74)
Initialize the cli command in two phases. Support the ping command while the agent is initializing Enable the full cli once the agent has finished initialization (cherry picked from commit 8ca14bc)
Remove unused fields Add training in progress per dimension (cherry picked from commit 4c33144)
Summary is not the default (cherry picked from commit 9b9ee3f)
…data#21200) (cherry picked from commit 86e73a2)
* Call maintenance functions from metadata event loop Remove service (MAINTENANCE) thread * run_maintenace every 10 seconds (cherry picked from commit ef816f8)
Restrict db.update_every to metrics selected for querying (cherry picked from commit c7f7929)
(cherry picked from commit b74aa71)
) * Correctly split MCP registry update to it’s own workflow. This needs to trigger when your releases are actually published, not when we start the release process, so it needs to have it’s own workflow with a release trigger instead of being part of the release workflow (as we always manually publish the release on GitHub). This actually simplifies a couple of parts of the job as well, since the `release` event defaults to using the commit of the release that triggered the workflow when checking out the repository. * Address review comments. (cherry picked from commit 81acfc8)
(cherry picked from commit 580f93e)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/ci
area/collectors
Everything related to data collection
area/daemon
area/database
area/health
area/ml
Machine Learning Related Issues
area/packaging
Packaging and operating systems support
area/web
collectors/cgroups
collectors/windows
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.
Summary