Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade snappyer and crc32cer deps to support windows #73

Merged
merged 1 commit into from
Mar 26, 2020

Conversation

zmstone
Copy link
Contributor

@zmstone zmstone commented Mar 26, 2020

No description provided.

@k32
Copy link

k32 commented Mar 26, 2020

This commit changes how NIFs are searched. Could you please elaborate why NIFs should be searched in the new places? Code paths is something that I would consider security-sensitive part.

zmstone/crc32cer@8ccf8ac

@zmstone
Copy link
Contributor Author

zmstone commented Mar 26, 2020

that's a revert to old code as in 0.1.3
please inspect the diff between 0.1.3 and 0.1.4

@k32 k32 merged commit fd7c4a1 into kafka4beam:master Mar 26, 2020
turtleDeng pushed a commit to emqx/kafka_protocol that referenced this pull request Jan 11, 2021
* Produce request encoding performance improvement (kafka4beam#69)

* Improve produce request encoding performance

Also added a simple eunit test to benchmark
produce request encoding before/after performance
this patch speeds up encoding around 35%

* Allow #kpro_msg.msg to be iodata()

* Delete remote call to iolist_size

* No need to make binary for enif_inspect_iolist_as_binary

The naive idea was to ensure binary so nif should not need to
copy iolist as binary (it would take the already created binary directly)

* Avoid iolist_to_binary when encoding string

* Upgrade snappyer and crc32cer deps to support windows (kafka4beam#73)

* fix(connection): back pressure for send API even when no_ack

* chore(appup): pin version 2.3.6.1 and add appup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants