Handling of invalid/incorrect SSL options for gun:open

[akanashin]

Hey!
I'm observing strange behaviour here.
When calling gun:open and giving it incorrect/invalid SSL options (like conflicting options or missing file) it still returns {ok, Pid}. Connection fails.
But then, I'm working with gun in gen_statem process. And i'm not getting gun_up event (which is correct in such a case) but not any other events from gun process.
I can call gun:await_up and then it returns error in my case but the method waits for the connection to actually attempt to complete. Which is not well aligned with FSM ideology i use.

I'm able to get signals about errors by monitoring Pid returned from gun:open. But this looks like some external hack.

So now the question: is there any better way to do that? Maybe some options for gun:open?
Thanks

[essen]

Gun should fail eventually depending on the retry and retry_timeout options. In your case you probably want to disable those, then you'll likely get the error quicker, assuming there isn't another issue.

[akanashin]

I have retry=0 in options. But no luck....

[essen]

Set trace => true and let's see what it prints.