-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Library does not work anymore with boost 1.87 #1157
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
Comments
this branch has fixes if anyone's interested : https://github.com/jcelerier/websocketpp/tree/ossia/2024-12-18 |
@jcelerier Good jods. But I have some bugs to report:
|
what is your failure with start_accept ? do you have a repro ? |
I put up a PR that addresses this. Please see #1164 and provide feedback on if it works for you or not (I've not tested it in EVERY scenario possible...just the ones that I'm actually using in my product). |
@toonetown That is actually my pull request, we created almost identical fixes for the issue within minutes of one another (you beat me by about 20 minutes 😄), yours is #1163 |
@amini-allight - so funny! They were so similar I didn’t even realize that I linked the wrong PR in my message above! I like how we both were even pretty similar (and a little bit snarky) in our PR details… 😂 This project seems to be completely unmaintained (no activity at all on the develop branch in over 3 years and I haven’t come across any recent messages at all from the maintainer on the issue board), so it would probably be useful to have a single “reference” patch that can be used. I will try to find time this weekend to review your PR and maybe we can reconcile any differences (I doubt there are many, if any) and if we can do so, I can close mine so there aren’t multiple PRs for the same issue. I also track a pretty “bleeding edge” code base (where “bleeding edge” really just means “doesn’t rely on APIs deprecated 8 years ago” 😂)…so from a personal perspective, it would be nice to also have a single patch that could potentially be updated in the case of future breakage as well. |
@toonetown Sounds great, I'll be happy to make any changes you advise! |
Thank you so much! It's surprising this hasn't surfaced earlier. Relevant fixes must be ported IMHO. |
The text was updated successfully, but these errors were encountered: