Jonathan Schaeffer

No, I worked a lot on it and could'nt get the right settings. I have similar issues with other deployments and ingresses. So the problem may not be related to...

Hello, thanks for taking the time. There is my ingress: ```yaml --- apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: pgadmin spec: rules: - host: pgadmin.resif.fr http: paths: - path: / pathType:...

I think it came as a dependency of eflambe. ``` grep meck mix.lock "eflambe": {:hex, :eflambe, "0.3.1", "ef0a35084fad1f50744496730a9662782c0a9ebf449d3e03143e23295c5926ea", [:rebar3], [{:meck, "0.9.2", [hex: :meck, repo: "hexpm", optional: false]}], "hexpm", "58d5997be606d4e269e9e9705338e055281fdf3e4935cc902c8908e9e4516c5f"}, "meck":...

You've pinned it. Thank you. I needed to explicitely put meck in my mix.exs in order to be included in the release. Is this normal ? Now, with meck explicitely...

Thanks again for your help, I really appreciate it. Searching documentation about `debug_info`, I made the following: In mix.exs: ``` def project do [ app: :wsdataselect, ... elixirc_options: [debug_info: Mix.env()...

I'm looking into this. Thank you. Side question: all those settings needed, make me wonder if using eflambe into a release is the right way to do ? Sould I...

You nailed it. I added `strip_beams: false` in my mix.exs and got a nice bggg file. transformed it to svg using https://github.com/brendangregg/FlameGraph and could work with the output. Thanks again...

Uuhhh, I just saw your video tutorial ... I should have started from there. https://www.youtube.com/watch?v=fRNdej-UXKQ

Hello, same problem here with fr_oss layout.

Lib tzdata got bumped to fix this issue (https://github.com/lau/tzdata/releases/tag/v1.1.2) See issue https://github.com/lau/tzdata/issues/143