David Aronchick

Trying to track this down - there's a bug where you request more concurrency than available. Repro: ``` make devstack-one #Create a devstack with 1 node go run . docker...

``` // TODO: We throw an error into our logs for every user error, we should split. If they have a bad binary, that's their fault, not ours. ``` https://github.com/filecoin-project/bacalhau/blob/757b7e504caee0e31d5fe565c52e67c5790f9263/pkg/computenode/shard_fsm.go#L474

``` // TODO: Get a lot of these, should we care? 'Bidding ignoring unknown action: ActionBid [NodeID:QmUhzQME]' ``` https://github.com/filecoin-project/bacalhau/blob/757b7e504caee0e31d5fe565c52e67c5790f9263/pkg/computenode/shard_fsm.go#L370

https://github.com/filecoin-project/bacalhau/blob/757b7e504caee0e31d5fe565c52e67c5790f9263/pkg/requesternode/shard_fsm.go#L364

``` // TODO: Same as 829 in pkg/eventhandler/chained_handlers.go ``` https://github.com/filecoin-project/bacalhau/blob/757b7e504caee0e31d5fe565c52e67c5790f9263/pkg/publicapi/handlerwrapper/log_handler.go#L26

``` // TODO: Is checking environment every event the most efficient way to do this? Could we just shunt logs to different places? ``` https://github.com/filecoin-project/bacalhau/blob/757b7e504caee0e31d5fe565c52e67c5790f9263/pkg/eventhandler/chained_handlers.go#L106

``` // TODO: Potential hotspot - json.Marshaling is expensive, and we do it for every event. ``` https://github.com/filecoin-project/bacalhau/blob/757b7e504caee0e31d5fe565c52e67c5790f9263/pkg/eventhandler/chained_handlers.go#L96

Add download and run canary

2

Is there a way to download and run from latest public? Or an alternative canary that detects if there's a version skew? I don't think we need to do it...

Docker throws errors when shutting down devstack

1

Probably low pri - but ``` ^C15:24:03.21 | INF bacalhau/devstack.go:151 > Shutting down devstack 15:24:03.417 | ERR system/cleanup.go:85 > Error during clean-up callback: close tcp4 0.0.0.0:60267: use of closed network...

We need to rename this - what does it mean to be "furthest along" for a job? Closest to final?

1

``` // TODO: We need to rename this - what does it mean to be "furthest along" for a job? Closest to final? ``` https://github.com/filecoin-project/bacalhau/blob/bf4da6850444d4f312bb2186d8943c32d0036702/pkg/job/job.go#L111