Cafe137
Cafe137
When uploading a single large file, e.g. mp4 of size 250MB, the "Aw, Snap!" browser crash happens. This is due to the whole file being in memory and the browser...
It seems to be suboptimal UX and may cause confusion that the upload finishes quick, yet the content is not accessible on the network yet. Remediations: - Explain the data...
e.g. `LightModeRestart.tsx`: ``` if (Date.now() - startedAt < 45_000) { return } ``` When restarting, we also wait 5s IMO these are no longer necessary, or can be way shorter
Our `Rpc.sendNativeTransaction` implementation needs a `string` for the `value` of the transaction. This was `this.dai.toBigNumber.minus(totalCost.toString()).toString()` before. I tried out the gift card fund feature with the fake-bee and even though...
**Bug** Once it triggers the error state, then it keeps it forever, even when opening it from scratch: **Refactor** Rename to TokenPrompt and generalise it a bit
Not sure if this is different when running in desktop mode. In standalone mode, RPC endpoint may be set to an arbitrary endpoint and no checks are done to see...
`POST http://localhost:8545/ net::ERR_CONNECTION_REFUSED` **EthereumConnectionCheck.tsx** By default, Bee expects a local node at http://localhost:8545. To use a provider instead, simply change the swap-endpoint in your configuration file.
We have two type of errors which spam the browser console One is a user error, where div is a descendant of p (e.g. ExpandableListItem) And the other comes from...
``` 2022-10-19 14:27:40 INFO [Bee] OPTIONS / 2022-10-19 14:27:40 INFO [Bee] OPTIONS / 2022-10-19 14:27:40 INFO [Bee] GET / 2022-10-19 14:27:40 INFO [Bee] GET /health 2022-10-19 14:27:40 INFO [Bee] POST...