Upgrade to support OTP 26+#1
Merged
Merged
Conversation
ammbot
approved these changes
Jun 27, 2025
Author
|
@ammbot please let me know how the test of the RC goes before I merge and tag a version to it. |
It works. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is a fix for an error with Fluxter and ERTS >= 10.5.3. Originally, Fluxter would include a hardcoded binary header to each write. This header contains the binary representation of the destination IP address, port, and optionally a prefix. The write itself was being issued as a plain
sendto the port that was failing with erroreinval. It is possible that there was a change in the way ERTS expects this header to be formatted. This PR patches Fluxter to use:gen_udp.send/4and drop the binary header to fix the issue.