Luiz Fonseca

@harrywrok I'm not 100% sure, but you probably need to call `contentful.processForAllLocales` -- as in, you need to process the upload data, as seen in this test: https://github.com/contentful/contentful-management.js/blob/22f1e5ecfa98146426a6e9c43ab7adf4eccab78a/test/integration/asset-integration.js#L126-L147

@harrywrok Not sure if you've solved this, but can you double check if the blob/stream is being passed correctly? If you access that image, you will find in your inspector...

@harrywrok otherwise, maybe `readFile` is what you want https://github.com/joltup/rn-fetch-blob/wiki/File-System-Access-API#readfilepath-encodingpromise

MacBook Pro (16-inch, 2019) Having the same issue as well, basically caused by long-running commands (e.g. compiling output from web pack, compiling output from storybook) I only have 2 tabs:

On my side I haven't seen it crossing the GB mark anymore and I have been running it with a lot of tabs/commands/history

Do you have `PeerOptions` configured by any chance? (if so, check `read_timeout`)

+1, This would be a nice addition (currently I can't "override" specific configs env-wise)

@fri0z > Am I moving in the right direction? Yes! It's always tough to test everything, but it's how I'd move too. > During the development process, a question arose....

Ah yes, that's the same line of thought, basically all upstreams injected into => `proksi:route:`. I can check what needs to be done in the `RouteStoreContainer`

I've been thinking about this as well, torn between 2 different paths: - if we need to store, SQL would be best but it will require some sort of background...