silvpol

Thanks for prompt reply. I have found #3 after posting and I think I understand the tradeoff. My main concern is that I could end up runnig changes against the...

Thanks. Re 1 - I agree, not worth it Re 2/3 > These two are very similar and have the best potential. > The biggest problem is this can only...

Rolling back doesn't fix the issue, it just changes behaviour, the issue is present in both versions. One of the places causing issue is signature of setID function in DefaultBroadcaster:...

I've crated a simple example that allows to replicate the issue, I've published it on GitHub https://github.com/silvpol/atmosphere-issue-1988. I'm not sure what your dev setup is like, but if you use...

@nickva I have tested and it also happens in a db with just a single doc. Inserting custom reduce funtion via API is not restricted and causes **ALL** views in...

@trickkiste I have changed data design a bit to make it work with built in functions, using an array type to emit intermediate calculations and _stats function to achive what...

@maxisam You can also use chart's built in features - `extraInitContainers`, `containerSecurityContext.allowPrivilegeEscalation: true` and `extraVolumes` to replicate the old behaviour ````yaml sysctlImage: enabled: false extraInitContainers: - name: init-sysctl image: volumeMounts:...

It works if you change it manually on the automatically-provisioned Cloud Run service. The Cloud Run service has same name as the Cloud Function so you can just use it's...

I don't think this is a bug yaml.v3, more of a consequence of how it's processing and outputting. Our original file had quotes, but SOPS output doesn't retain them. Original...

It's more complicated than that, Dropwizard uses it as pre-parser so even if it endcodes characters it still doesn't help as encoding works only in quoted strings.