John Calvin

@Murderlon given this recent PR https://github.com/transloadit/uppy/pull/4037 is there any interest in reconsidering this?

I traced the sequence of events. After restoring a file and clicking "Upload": 1. tus.upload(file) called https://github.com/transloadit/uppy/blob/main/packages/%40uppy/tus/src/index.js#L186 2. Golden retriever receives `handleRestoreConfirmed` and calls uppy resume all. https://github.com/transloadit/uppy/blob/main/packages/%40uppy/golden-retriever/src/index.js#L307 3. Upload...

I played around with trying to fetch a fresh state of the file inside that qRequest function but calling `uppy.getFile` inside that function returns the old file state as well....

Sounds like the issue is fixed here but still waiting on a package release with it https://github.com/tus/TUSKit/pull/143

Past issues: - [gRPC PR #34177](https://github.com/grpc/grpc/pull/34177) - Fix that replaced `strdup` with `gpr_strdup` (merged Sept 2023) - [gRPC Issue #27995](https://github.com/grpc/grpc/issues/27995) - Original "Segmentation fault" on Alpine Linux report - [gRPC...

Also confirmed the segfault occurs in ruby 3.1, as well as Alpine 3.20

> Have you tried install `grpc` with `--platform ruby`? It could be related to not having precompiled gems for musl environments: [#39443](https://github.com/grpc/grpc/issues/39443) Yes, Gemfile is specified like `gem "grpc", "~>...

Yep, that did it ``` gem "google-protobuf", force_ruby_platform: true gem "grpc", "~> 1.73", force_ruby_platform: true ``` This is resolved for me, thank you.