raulk

HTTP is designed to be synchronous though, so the client has an expectation that the response will be almost immediate (and/or the server is starting work immediately). However, the graphsync/data-transfer...

@dirkmc On a restart of the transfer or the host, how hard would it be to reset the transfer back to `Requested` and then transition it to `Receiving` the moment...

1. What I'm observing is that the opening blocks entirely -- it does not fail immediately. 2. Whitenoise is already setting the retry params: https://github.com/raulk/whitenoise/blob/master/testplan/main.go#L105-L113

This is just a single test, nothing fancy. Things should be configured the way we set them up in Lotus. Could you try running the basic composition in the whitenoise...

Yeah, and sending all CIDs scales very poorly. We should never do that!

@jennijuju it looks like this has garnered the desired level of approvals. Should we go ahead and merge to formally relieve outgoing FIP editors of their duties? (We seem to...

We need to make room for engineering-oriented projects that don't have an immediate product outcome/result, but directionally set us up to deliver with higher quality, speed, and confidence. I think...

Likely to be folded into #13.

@acruikshank and I hacked on this during Hack Week! I present to you "the Bounty Actor": https://github.com/acruikshank/specs-actors/tree/feat/bounty_actor, which can work with normal FIL or Tokens!

@Gozala I think what you're thinking of here is already covered in #21 -- Project Flare, much of which has already been implemented.