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

fix-panic #72

Merged
merged 1 commit into from
Apr 19, 2022
Merged

fix-panic #72

merged 1 commit into from
Apr 19, 2022

Conversation

BoskyWSMFN
Copy link
Contributor

fixed runtime panic in server/internal/circ/pool.go occurring on 32-bits architectures caused by misalignment of BytesPool struct members.

golang/go#36606 (comment)

fixed runtime panic in server/internal/circ/pool.go occurring on 32-bits architectures caused by misalignment of BytesPool struct members.

golang/go#36606 (comment)
@coveralls
Copy link

Pull Request Test Coverage Report for Build 2186201474

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 98.564%

Totals Coverage Status
Change from base Build 2160369992: 0.0%
Covered Lines: 2676
Relevant Lines: 2715

💛 - Coveralls

@mochi-co mochi-co merged commit b53774f into mochi-mqtt:master Apr 19, 2022
@mochi-co
Copy link
Collaborator

Good catch @BoskyWSMFN - I caused this in the v1.2.0 update. We need to find an easy way to check 32bit runtime...

Merging and releasing v1.2.1 👍🏻 Thank you!

@BoskyWSMFN
Copy link
Contributor Author

Good catch @BoskyWSMFN - I caused this in the v1.2.0 update. We need to find an easy way to check 32bit runtime...

Merging and releasing v1.2.1 👍🏻 Thank you!

The easiest way is raspbian as far as I can see.
I compiled this broker for arm-32 system and caught the panic there so I can provide some feedback about compatability if I find something.

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.

3 participants