-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[RELEASE] Downgrade version 2.6 to boost 1.83 #5759
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
Conversation
release
branch only, downgrade to boost 1.83
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release #5759 +/- ##
=========================================
- Coverage 78.8% 78.8% -0.0%
=========================================
Files 814 814
Lines 71345 71310 -35
Branches 8357 8345 -12
=========================================
- Hits 56234 56192 -42
- Misses 15111 15118 +7
🚀 New features to boost your workflow:
|
Additional details: Version 1.86 of boost introduced a regression bug in This crash might produce a stacktrace from
Frame 7 refers to an exception thrown (in The reason why there's no executor is explained in boostorg/beast#2925 and the frame 17 shows the buggy function being called https://github.com/boostorg/beast/blob/fee9be0be10c9c9a22ac1505a710d1d8ed5a3dfb/include/boost/beast/core/impl/basic_stream.hpp#L329 (packaged with |
"packet timeout" so this is not triggered by specific transactions but potentially by random network activities? |
Roughly, yes. There must be a pending TCP activity which is causing timeout, and then the next network operation will result in a crash. We did not spend much time looking for the reproduction of this bug, so I cannot tell you much more. |
bba7b4b
to
8d01f35
Compare
NOTE this is for
release
branch onlyHigh Level Overview of Change
This fixes a problem where
rippled
could crash due a regression bug in boost 1.86Context of Change
This is the result of an internal investigation into
rippled
crashes in testnet. We found the crashes to correspond to a documented regression in boost 1.86 and confirmed that this bug is not present in the older version of boost 1.83 , which was used before #5264 . We do not fully revert this PR since there is no need.Type of Change