MOZGIII

@gildor what makes you think it's expected behavior? I think there are tests that try to test json to be parsed into UTF-8, but they don't handle this case for...

Oh, got it. That's not the case for me though, since I use `call.receive()`. I think the default behavior is incorrect. Either we should not call `receiveText` for JSON input...

I'll check if my issue is resolved later today and post an update here.

I updated my code to use ktor 1.1.3, and it seems like the issue does not appear anymore. That said, I'm not sure if it's fixed or if I forgot...

I started with this, and pretty quickly hit the complication: benches are not adopted for our cross-compilation machinery, and it will take some extra steps to make them work right...

Maybe this can be resumed after #910 is done?

We actually require it for integration with postgres operator. ```yaml extraEnv: - name: DB_USER valueFrom: secretKeyRef: name: hydra.hydra-db.credentials.postgresql.acid.zalan.do key: username - name: DB_PASSWORD valueFrom: secretKeyRef: name: hydra.hydra-db.credentials.postgresql.acid.zalan.do key: password -...

Well, disabling the secret entirely might not be a good idea, since other values are kept there (system and cookie secrets). But it would make sense to, maybe, separate the...

Added a small fix for incorrect use of `unset` instruction at configmap

> Am I to understand that in your use case, you receive the DB credentials from the cluster, and have to construct the DSN on runtime? Yes, that is correct...