Bump libs/EXTERNAL/sockpp from 599f750 to 04002da

[dependabot]

Bumps libs/EXTERNAL/sockpp from 599f750 to 04002da.

Commits

• 04002da Merge pull request #94 from JaanDev/master
• 10a706b remove vscode folder
• 8549d2d fixed not compiling on windows clang
• 81328fb Minor update to README
• a4a5f37 Fixed the streaming create_handle() to return a result.
• c21fc77 Acceptor doesn't reuse by default. Created a global text/example port constan...
• d86b29f Started adding socket options. Changed the acceptor reuse option to specific ...
• b2585e4 Cleaned up examples and result. Moved some chrono into sockpp namespace.
• 7a238ee Removed socket::last_error() and cached lastErr_ member. Implemented result<>...
• f0012a2 Updated CMake build to C++17
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vaughnbetz]

@AlexandreSinger @w0lek : looks like there is an update in sockppp. Should we pull it into our version? (I think we're using our own version)

[w0lek]

@vaughnbetz,
We used fork of sockpp with a few warning compilation fixes, which wasn't pushed to sockpp master. I forgot to do PR for sockpp to push our changes to master, i will do it on mondaM. Also we have a plan to migrate from sockpp to boost.asio, but i don't know when exactly this should happened. So with respect of plan to move to boost.asio, i am not sure if it make sense to update sockpp now.
FYI @AlexandreSinger

[vaughnbetz]

Thanks. Sounds like I should not merge this then.

I think raising a PR to push your changes back to sockpp makes sense. Moving to boost.io is an optional thing in my opinion. 

[w0lek]

@vaughnbetz, @AlexandreSinger
Additional information about sockpp update. We use fork from branch v1.x tag v1.0.0, which is latest stable release.
So that means, now is better to not update sockpp. According to sockpp contribution flow, we need branch from develop and contribute to develop, which is ahead further compare to v1.0.0. I need some time to move my changes to develop branch, check there is no any new compilation warnings arise with new code from develop, and make a test. Since we have a plan to move to boost.io, i need to speak with team to make a conclusion what way we should go.

[vaughnb-cerebras]

Thanks, and no rush to upgrade. I am fine with staying with the older version; I just watch these dependabot updates to stay up to date where we can.

[dependabot]

Superseded by #2957.