lua: fix typo specifying \0 byte as /0 #8251
Open
+9
−9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
serprex
added a commit
to PeerDB-io/peerdb
that referenced
this pull request
Mar 9, 2024
So this turns out to be less easy than I thought a few hours ago Flatbuffers is pretty bad, the lua side hasn't been touched for 3 years yet I found a silly typo just flipping through the code: google/flatbuffers#8251 In particular, they seem to assume string.pack/string.unpack will exist, but in 5.1 it doesn't, with LuaJIT they use ffi which means that works out for most 5.1 users Solution: we're going to shim our own go implementation of the flatbuffers lua library
serprex
added a commit
to PeerDB-io/peerdb
that referenced
this pull request
Mar 10, 2024
So this turns out to be less easy than I thought a few hours ago Flatbuffers is pretty bad, the lua side hasn't been touched for 3 years yet I found a silly typo just flipping through the code: google/flatbuffers#8251 In particular, they seem to assume string.pack/string.unpack will exist, but in 5.1 it doesn't, with LuaJIT they use ffi which means that works out for most 5.1 users Solution: we're going to shim our own go implementation of the flatbuffers lua library
serprex
added a commit
to PeerDB-io/peerdb
that referenced
this pull request
Mar 10, 2024
So this turns out to be less easy than I thought a few hours ago Flatbuffers is pretty bad, the lua side hasn't been touched for 3 years yet I found a silly typo just flipping through the code: google/flatbuffers#8251 In particular, they seem to assume string.pack/string.unpack will exist, but in 5.1 it doesn't, with LuaJIT they use ffi which means that works out for most 5.1 users Solution: we're going to shim our own go implementation of the flatbuffers lua library
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Probably a code path that never runs