Francesc Alted

BTW, after the discussions you still think that a 64-bit header is a good idea for c-blosc itself?

@GlenHertz just to be clear, c-blosc supported 64-bit compilation mode since the beginning. What we are talking about here is to possibility to have buffers larger than 2 GB (32-bit)....

@psychocoderHPC Sorry but there are no plans for suppoting 64bit buffers in Blosc 1. You might be interested in [Blosc2](https://github.com/Blosc/c-blosc2) which has full 64bit support for buffers. And although Blosc2...

Yes, I agree that the keyword approach sounds sensible. What about `safe=True` instead of `unsafe=False`? (double negation always takes a few more brain cycles to process ;)

I did some fixes in the ndlz code, but still having issues with one: https://github.com/Blosc/c-blosc2/runs/5848395013?check_suite_focus=true . @oscargm98 could you have a look at this one? You can still use the...

I have started a new `fix-fuzzer` branch for fixing this. @oscargm98 please use the new one instead.

@oscargm98 I have just merged `fix-fuzzer` branch (via PR https://github.com/Blosc/c-blosc2/pull/391). But the issue mentioned above is still there, so help would be appreciated.

In the end that was fuzzer trying a new path, and not related with zlib-ng (fuzzer triggering when updating to the latest version of it was just a coincidence, I...

Yeah, here the issue is due to the fact that when `typesize` is 1, the shuffle is doing nothing, so I decided to silently switch off the filter internally. But...

As stated in the [README](https://github.com/Blosc/c-blosc/blob/main/README.md#compiling-the-blosc-library), in order to compile C-Blosc you need first to create a build directory and run the compilation from there.