Guido Maria Serra+Fenaroli
Guido Maria Serra+Fenaroli
trying to use the `--spec=https://gitlab.com/gitlab-org/gitlab/-/raw/master/doc/api/openapi/openapi.yaml` > site-packages/http_prompt/cli.py:119: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details. > spec = yaml.load(content)...
seems that the helm chart for cerebro is getting deprecated charts.helm.sh https://github.com/helm/charts/tree/master/stable/cerebro I can give a hand to migrate it here using GitHub pages as hosting... but I need someone...
ok, I'm on ur latest stable `v2.4`... seems that for traffic originated from the same subnet (in my case I have kubernetes nodes with an F5 in front) ...the traffic...
running with a docker container built with package datadog-dotnet-apm_1.28.8_amd64.deb we need to have HTTP_PROXY env settings for the main application, but I also need to disable it for the DD_tracer...
`tls: failed to find any PEM data in certificate input` this is all I get back... my KUBECONFIG is properly set, I daily work with it switching between several configurations...
decoding the base45 string obtained by my tool https://github.com/zeph/qr_encode_disaster_recovery from the Green Pass I just got on my Immuni App fails miserably with a decode error... same happens attempting with...
``` /home/gms/.rvm/gems/jruby-9.2.9.0/gems/logstash-core-5.6.4-java/lib/logstash/settings.rb:476: warning: constant ::Fixnum is deprecated /home/gms/.rvm/gems/jruby-9.2.9.0/gems/logstash-core-5.6.4-java/lib/logstash/settings.rb:480: warning: constant ::Fixnum is deprecated /home/gms/.rvm/gems/jruby-9.2.9.0/gems/logstash-core-5.6.4-java/lib/logstash/settings.rb:503: warning: constant ::Fixnum is deprecated /home/gms/.rvm/gems/jruby-9.2.9.0/gems/logstash-core-5.6.4-java/lib/logstash/settings.rb:507: warning: constant ::Fixnum is deprecated --- jar coordinate com.fasterxml.jackson.core:jackson-databind already...
it is a very simple PR, it just enables the debugging of SSO integration that turned out to be pretty challening without extra logging as for instance, by default Azure/Entra-ID...
This is a feature request to be able to add a transitioning tier rule to a bucket. Since there is already a Rule definition, but is related to `expiration` only...
(wrongly felt) it works for us on single container, but it won't stand a reboot (see: https://github.com/kubernetes-sigs/kind/issues/2879#issuecomment-2472643645) on Debian 12 (installing `bookworm-backports` for nvidia drivers) we have tons of Pods...