fasterthanlime, 4 months ago

this was, in fact, because I started namespacing stuff harder and you can't access secrets cross-namespace, so the k8s solution is, of course, to install emberstack/reflector which monitors and copies secrets/configmaps to other namespaces https://artifacthub.io/packages/helm/emberstack/reflector

fasterthanlime, 4 months ago

yes this is a completely reasonable response to me getting the YAML slightly wrong, good job golang

groxx, 4 months ago

@fasterthanlime nulls were a mistake.

So of course Go chooses to make them even harder to spot, with implicit dereferences and interfaces everywhere.

:blobfoxnotlikethis:

lesto, 4 months ago

@fasterthanlime
https://imgflip.com/i/8b3j1w

ivan, 4 months ago

@fasterthanlime YAML - so you can achieve a segfault without even needing to recompile

mel, 4 months ago

@fasterthanlime ugh that can’t be the actual correct behavior of the package right?

fasterthanlime, 4 months ago

@mel this isn’t the YAML parser, it’s later parts of the code accessing pointer fields it assumes are initialized