Ian Seyer

yes - even after using enter to rotate to the correct pod, pressing `r` still opens to the default container

Also getting this error. Deploying a flask application that uses boto3. Have a single POST route, slim_handler is `false` and there is sufficient memory (512mb). Very frustrating.

On following boots, I get: ``` java.lang.IllegalArgumentException: Wrong definition: " int_id: vcs_root_int_id M defines -- refers TODO return refers when vcs_root table is populated". at jetbrains.buildServer.serverSide.db.schema.SchemaDefBuilder.buildTableDef(SchemaDefBuilder.java:244) at jetbrains.buildServer.serverSide.db.schema.SchemaDefBuilder.buildSchemaDef(SchemaDefBuilder.java:74) at jetbrains.buildServer.serverSide.db.DBSchema$1.call(DBSchema.java:58)...

Just a rogue developer passing through, but IMO it would be great for solution architects to be able to see from the documentation how µraiden handles certain edge cases without...

Seconded - would also like to see an arm release

This would be especially nice for our current use case, where we want to have multiple internally hosted gateways behind an ingress/application load balancer for path-based routing to individual gateways...

bump, exact same issue

Also confused - `helm-wrapper` was removed with this commit: https://github.com/futuresimple/helm-secrets/commit/b9c533fc889a44a0aa9c56ffc01c425933f58600#diff-88629586a25c07db6c7afb978d4f6cbc What is the resolution for this? Now my helm installs/upgrades are not decrypting.

+1

To be clear - the chunksize increase "works" insofar as it prevents chunking below a certain threshold. You are passing the buck to the memory of your registry instance.