Sebastián Greco
Sebastián Greco
Hi, The way nodes are added/removed from the [list of nodes](https://github.com/metallb/metallb/blob/main/speaker/layer2_controller.go#L105) leads to 2 non-desired behaviours as they will cause disruptions for connections. 1. Joining/Deleting a node from the cluster...
**What steps did you take and what happened:** Resources that are in violation of a constraint, can't be deleted from ArgoCD with "foreground" delete (default for ArgoCD). ArgoCD stays in...
https://github.com/docker/cli/blob/a32cd16160f1b41c1c4ae7bee4dac929d1484e59/cli/command/system/prune.go#L131 Currently is not possible to execute prune operations using filters to exclude with "OR" logic. Assume one would like docker system prune to exclude all resources with either one...
UseContainerSupport is [backported to Java 8u191](https://www.oracle.com/technetwork/java/javase/8u191-relnotes-5032181.html) and should be used instead of the experimental flags. https://github.com/sonatype/helm3-charts/blob/775f49bd3d2ea40ccf6d21d891adc6409bd08dbf/charts/nexus-repository-manager/values.yaml#L24 Current configurations that would default to UseContainerSupport can be seen: java -XX:+PrintFlagsFinal grep "InitialRAMPercentage\|MinRAMPercentage\|UseContainerSupport\|MaxRAMPercentage"
Every now and then, we see this error in our CodeQL scans. Both default and "advanced" ones: ``` Written by John Gilmore and Jay Fenlason. Found gnu tar version 1.34....