Jason Yundt
Jason Yundt
OK, so based on your response and the little that I already know about using Node.js, here’s what I need to do in order to make sure that my Node.js...
> The first dialog with the path to the crash dump will be shown **after** the crash dump was successfully written by Windows `MiniDumpWriteDump()` function. > Do you have a...
> That's the thing, you should only get one of the dialogs **not** both. Unless it just crashed again and couldn't write the dump the 2nd time. But I can't...
> I am sad, I can't use my retro rig with a Voodoo3 / Voodoo5 card anymore because 1.5 would not run on the Windows 98 I need because drivers...
> So is this working now as well, then, if [#809](https://github.com/koverstreet/bcachefs/issues/809) is working? I just tried reproducing this bug on an ext4 VM and a bcachefs VM. The build succeeded...
> Can you try with 6.14-rc1? That fixed a similar issue with nodejs I just tried it with the two VMs again, this time with Linux 6.14.0-rc2. It succeeded in...
> Try setting the `str_hash` option to `crc32c`. I just tried it with the two VMs again. This time, I used Linux 6.14.0-rc4 for both VMs and I used the...
> Which kernel version were you using with bcachefs? Thank you for asking this question. It helped me realize that I made a mistake. I took a look at both...
This issue was fixed when the patch from #624 was accepted.
> And just out of curiosity, do you have a particular use case for the filesystem backend + JSON serializer with large responses? Not really. When I first stared using...