Joshua Scott

This just gives me `Unknown application :persistent_term` in the dialyzer run

I was unable to reproduce in erlang with the following steps: ``` # persist.erl -module(persist). -export([set/1, get/0]). set(Val) -> persistent_term:put(foo, Val). get() -> persistent_term:get(foo). ``` ``` $ dialyzer --build_plt --apps...

😕 dialyzer doesn't complain in plain erlang, though, so it seems like it wouldn't be an OTP bug? What am I missing?

The workaround is to ignore those warnings: in `mix.exs`: ``` def project do [ # other configs not shown dialyzer: [ ignore_warnings: ".dialyzer_ignore", ] ] end ``` create a `.dialyzer_ignore`...

@WarpRat I haven't gotten any workaround. We basically just have to re-plan when it happens, which is maybe once/day. We had a test where we were running terragrunt-atlantis-config in travis-ci,...

@WarpRat are you using `sops_decrypt_file()` by chance? It seems like when I remove that from our configs that the generate works without throwing this error.

We also are using the 2.x master, and it works well. I would highly recommend going that way for a new project.

I think autocreation could be an option; I'd be concerned about doing it by default. I think returning an error at creation vs crashing is basically the same thing, since...

Having worked with a number of backpressure systems, I feel as though it may be overcomplicating things to provide backpressure as part of the consumer group behaviour. When I've used...

@dantswain do you think this can be closed now?