As part of our effort to remove data plane exceptions (@asraa @yanavlasov), we probably should fix the explicit usage of exceptions in this extension.

Authors and content exercise writers may request from the community to contribute new exercises.
To do so Exercises and sections can be flagged as incomplete with a request for help to complete and an appropriate message will be rendered in the UI as the user accesses the section or exercise.

@ChristopherDavenport has been arguing for this, and I like @SystemFw's argument about not burying use.

Steps:

1. Add @deprecated annotation to both overloads of Client.fetch.
2. Replace client.fetch(req)(f) with client.run(req).use(f) in tests and docs.

Bonus

Some of the benchmarks don't have the correct scala doc, fixing those.

• https://github.com/monix/monix/blob/master/benchmarks/vnext/src/main/scala/monix/benchmarks/AsyncQueueBenchmark.scala#L41
• https://github.com/monix/monix/blob/master/benchmarks/shared/src/main/scala/monix/benchmarks/CoevalAttemptBenchmark.scala#L38
• https://github.com/monix/monix/blob/master/benchmarks/shared/src/main/

java.lang.IllegalArgumentException: Argument not supported by ScalaTest-js: -C
	at org.scalatest.tools.ArgsParser$.parseArgs(ArgsParser.scala:191)
	at org.scalatest.tools.Runner$.runOptionallyWithPassFailReporter(Runner.scala:883)
	at org.scalatest.tools.Runner$.run(Runner.scala:850)
	at org.scalatest.tools.Runner.run(Runner.scala)
	at org.jetbrains.plugins.scala.testingSupport.scalaTest

Currently websockets are unsupported:

class SttpBackendStub[F[_], S] private (
    monad: MonadError[F],
    matchers: PartialFunction[Request[_, _], F[Response[_]]],
    fallback: Option[SttpBackend[F, S, NothingT]]
) extends SttpBackend[F, S, NothingT] { // TODO

(note the TODO for the NothingT type parameter which specifies what kind of websockets are supported).

The bac

Concerning Postgres versions:

1. It should be clarified & documented which Postgres versions are supported
2. Tests should be added for each supported version

Currently, we manually append the params to the url / query string using urljoin. Instead, we can send the query params in as a dictionary

Spotted in the gitter channel

The big thing for me was that it wasn't clear that the cache could be reused. It talks about the state monad and the cache being immutable which caused me to make some bad assumptions, even after diving into the code.

This should be more explicit and clear to not confuse people.

I see that x-server-raw-response is available to expose the underlying to users, allowing deeper customization of response.

I was wondering if it's possible to expose a similar interface for request as well? So that we can utilize some predefined functions by akka-http. For example, extractClientIP.

Not a huge deal and is blocking anything, since we can simply replicate all these funct

The docs make it pretty clear how to make a request and decode the entity of the HttpResponse:

  val response = Hammock
    .request(Method.GET, uri"https://api.fidesmo.com/apps", Map())
    .as[List[String]]
    .exec[IO]

And you can get the headers like:

  val response = Hammock
    .request(Method.GET, uri"https://api.fidesmo.com/apps", Map())
    .map(_.headers)
    .

Hi

the train function returns two variables losses and samples. These two variables are never declared before. The article and documentation also don't explain these variables enough so I could fix it. Could you tell me how they should be declared and used?