Closed brianmay closed 2 years ago
Hi Brian, thanks for the detailed report! I do think this is a bug (and most likely related to https://github.com/appcues/mojito/issues/86)
I'm going to try to gin up a test case to try to reproduce what's happening locally to see if I can figure it out
Some extra data points, for most recent experiences:
I said 0.2 seconds, wonder if I misread that. Also some of these might be post requests (with relatively small data payload containing username/password) not get requests. Doubt it matters, everything else is the same.
I'd suggest that for the time being, you try a different client, mostly for the reasons stated here: https://elixirforum.com/t/mint-vs-finch-vs-gun-vs-tesla-vs-httpoison-etc/38588/11
We (Appcues) are in the process of switching to use Finch in basically all cases now, it just performs better
Thanks for the link, it is probably good to keep my options open. Will try Finch.
Hi! This project is now deprecated:
We recommend that you use Finch which is also built on Mint. The creator of Finch has an excellent writeup here describing the problems with Mojito, and as a result we use Finch internally at Appcues now.
My understanding is that all I need to do to handle errors is look at the result, e.g.
But I find on certain types of errors, I also have to implement the appropriate
handle_info
call.e.g. I got the error:
But my genserver died also, about 0.2 seconds later.
What seems strange is that this looks like a valid response. So maybe the problem is that mojito timed out, and then we got a response and mojito is confused by this response after it already timed out?
Am I expected to receive messages from mojito too (if so this should be documented in
README.md
)? Or is this message a bug?