Austin S. Hemmelgarn

I’m hoping to get this fixed in time for the release at the end of the month, but I’ve not had time to actually dig into this yet, so it...

I would vote for arbitrary message sizes, we should be future-proofing this if at all possible.

Reopening this so that the second part does not get forgotten. Target date for that is currently 3 months from now (2022-08-03).

@DShreve2 We ideally should have a reminder about this in the release notes. The PR to actually finish things here will probably not be ready before the release, but is...

This is something we’d like to do long term, but it’s very low priority right now, especially since we’re in the middle of reworking how we handle building and publishing...

The current WIP code for the packaging rework can be seen in #9964. The current plan once that is working correctly and merged is to work on getting packages building...

Reopening this as it’s not actually done and we are planning on doing it, the timeline has just slipped horribly because native package improvements have largely been low priority in...

Further update: This is currently stalled pending completion of the migration of our package repositories from Package Cloud to self-hosted infrastructure. It’s still on the TODO list though, it just...

This is theoretically doable, but not easy. GHA only provides 64-bit x86 environments. Unless that changes (not likely IMO, for multiple reasons), we have only two options for this type...

Most likely it’s seeing a `netdata` binary left over from a previous install (but not seeing an install type marker, hence can’t determine the install type). Running with `--reinstall` _should_...