harry lachenmayer

Hi there, we're still encountering this in production - this has crashed our servers on several occasions. The root cause is the following: 1. We're using the public `upload_stream` API....

I get this as well when I run any command that should render a help message, eg. `ssb-server --help`.

Hi @viglucci, thank you so much for your efforts on this - this would make our lives so much easier. If you'd like us to "beta test" any of your...

Hi @viglucci, I'm finally getting around to integrating RSocket 1.0 in a greenfield project, so I'll be adding to this thread as and when I find anything worth sharing. So...

Tiny tiny API inconsistency in the RxJS adapter: on the `RxRequestersFactory`, factories with input & output codecs are specified as separate arguments, while they're specified as an object on the...

Also another super tiny inconvenience in the RxJS requesters API: we're currently not using `metadata` in our client-side code (yet?), so we have to add `new Map()` for each `requestStream`...

Can confirm the fixed requesters API works great for us with `[email protected]`!

Hey Oleg, thanks so much for the quick reply! We're working around it for now by ensuring that we're setting `global.Buffer = Buffer` in our app before we do anything...

We ran into this issue ourselves, we're using the following fork: https://github.com/expo/expo-github-action/compare/main...lachenmayer:expo-github-action:eas-updates-qr You can use this with `uses: lachenmayer/expo-github-action/preview-comment@eas-updates-qr` to try it out, but please don't rely on it... This...

Hi there, we have been facing this issue for quite a while. We are using a resumable/chunked upload client called tus which uses `Blob#slice()` under the hood (see tus/tus-js-client#326 for...