3.5 is now stable version

i haven’t updated to the stable one yet though but usually I use intellij for Fuel

it works with 3.5 beta

downloading 3.5 stable

it works on 3.5 stable though?

what kind of error do you get?

Some kind of Gradle warnings

@kittinunf https://issuetracker.google.com/issues/130226195

basically unstable for kts project

I may not be online of this weekend over possible Tropical Storm or Hurricane Dorian hit.,

😱

take care bro!

Anyone knows why Fuel 2.x is so very slow when posting not even very large data (a few MB)? Anyone noticed this?

It takes 2 minutes to post 10MB to my own endpoint on the same machine

After getting back to Fuel 1.15.1 the same request is immediate

I'm just doing very simple

<http://Fuel.post|Fuel.post>(endpoint).body(byteArray)

And there is very large cpu utilization with this transfer - like it would process byte after byte without any buffering ;-/

I think this was fixed! The issue was a progress buffer and a shitty implementation. Have you tried the latest version?

@kittinunf I am safe from Hurricane.

https://github.com/kittinunf/fuel/milestone/3 Hmm

@kittinunf would you fix redirect looped forever?

@Derk-Jan Karrenbeld I think GET with body should be closed because Android implementations of HttpURLConnection forces it to POST if you set setDoOutput to true.

related to a past post (https://kotlinlang.slack.com/archives/C0B8GAGR0/p1565110311071200 and https://kotlinlang.slack.com/archives/C0B8GAGR0/p1565111788072600) , this code

val (request, response, downloadResult) = Fuel.download(it.downloadUrl)
                                        .fileDestination { _, _ -> tempFile }
                                        .authentication().basic(extension.stageReadUsername, extension.stageReadPassword)
                                        .awaitStringResponseResult()

is causing an OOM error during builds.

It appears to happen with large payloads, but I'm unsure why...

https://github.com/badoo/Reaktive interesting

But i wonder whether it is better to use Coroutine instead as they already have

Flow

it already challenging

RxJava's Single to Flow. Hmm

Android VM and Desktop JVM are different to handle query parameters?

Im not convinced on that …