Cafe137

Handle Bee status in Desktop to avoid HTTP API startup issues

1

Related: https://github.com/ethersphere/bee-dashboard/issues/499 and https://github.com/ethersphere/bee-dashboard/issues/558 Upon Bee launch, the HTTP API fires up and reports healthy and ready statuses. Contrary to this, some endpoints do **not** work for a short brief...

### Context ``` cors-allowed-origins: ["*"] ``` ### Summary I previously ran a dApp on `:5174`. Now I am running it on `:5173`. `GET /bytes/{...}` (and probably others, too) requests fail...

https://docs.ethswarm.org/api/#tag/Bytes/paths/~1bytes~1%7Breference%7D/head > Requests the headers containing the content type and length for the reference The content type is always `application/octet-stream`. If it is irrecoverable (only available in the mantaray metadata),...

Segmentation fault in reserve code

1

``` 2024-09-19 00:02:34 panic: runtime error: invalid memory address or nil pointer dereference 2024-09-19 00:02:34 [signal SIGSEGV: segmentation violation code=0x1 addr=0x50 pc=0xf8da36] 2024-09-19 00:02:34 2024-09-19 00:02:34 goroutine 655670 [running]: 2024-09-19...