Henrik Feldt

Strange. I don’t see how we could possibly have built against something that is not used in the fsproj (auto corrects to raptor 🦖)? But since we don’t use ifdefs,...

@cartermp Makes sense. We could recompile with a newer compiler if that would fix it.

@ivpadim Some guesses: set up mitmproxy, set it to very slow, then call https://discourse.mitmproxy.org/t/killing-tcp-connections/775 `flow.kill()`; alternatively, you could call Suave with a `Async.Sleep 1000` and directly cancelling the async token...

Http.fs should track this error and resend the request. PRs accepted.

@ChristopherLClark Did you find out the cause for this? I have configured retries, but the error doesn't just disappear on its own without restarting the process.

Yes, exactly. At one point in the chain of abstractions, so to speak. Actually, I'm thinking even lower-level than that; the linked article already has an implementation inside suave that...

I suggest it's colocated with http.fs to avoid divergence over time and that we cooperate on this repository without further name changes in that case. What do you think?

> We will need to publish two differents packages in order to not include Hopac and System.Diagnostics.FileVersionInfo dependencies on Fable apps. I suggest HttpFS.Core with the object model used by...

> point me to the code https://github.com/haf/Http.fs/blob/master/HttpFs/HttpFs.fs#L797 > I am ok to remove it, I just added it because it was present in elm-http-builder package. If users need to it...

Do we have to split the repo for this? Can't I give you complete access to this repo?