GP
@tetienne I noticed that the error in your workflow run logs is slightly different from the one reported in this issue. To help debug your issue, can you make this...
@tetienne The changes need to be merged before the action itself can kick in. In the run you linked, the CI ran with whatever's in your `master`; it needs to...
I’ve worked with `nvm` and `n` before, and had problems getting them to work correctly, especially with automated scripts — they’re usually executed by a CI/CD system that doesn’t use...
@Schniz Makes sense! Also I’d rather not even use `~` anywhere in my scripts. Quick questions — 1. Is `fnm exec` on the roadmap? Is there a branch or a...
@Schniz Whoa, `gpkg` looks great! > Symlinking `~/.fnm/current/bin/node` into `/usr/local/bin/node`. But again, I wouldn't do it. Can you expand on this? Why is this a bad idea?
[Indix](https://indix.com) uses KafkaJS to move massive amounts of data across various systems every day! We also open-sourced the [kafkajs-lz4](https://github.com/indix/kafkajs-lz4) module that we use in-house. Indix is a data-as-a-service company that...
@garmeeh +1 for this feature. Because this library doesn't support every Schema option, and because Schema could also change, it would be nice to have an escape hatch of sorts....
> I'm revisiting the implementation again and I have a PR ready to merge soon. @j0lv3r4 I see the PR is in Draft status. Is there someone we can do...
A stop-gap measure in the meantime can be pinning your `lz4` versions to `0.6.0`. In your `package.json`, you can add — ```json "resolutions": { "lz4": "0.6.0" } ``` Further reading...
FYI, adding `[jstype=JS_STRING]` to the `int64` fields has no effect.