upgrade to 2.23.1 of lsquic

[vhuynh3000]

No description provided.

[saltycrys]

Please also update the version in shard.yml.

[Perflyst]

@vhuynh3000 can you please take a look at the review from saltycrys?

[unixfox]

@vhuynh3000 can you please take a look at the review from saltycrys?

If @vhuynh3000 doesn't respond you or @saltycrys can update the code in the pull request and update the shard.yml. It shouldn't be too hard.

[Perflyst]

Right, but there is already v2.28.0, not sure if it's worth to update only to v2.23.1

[unixfox]

Well v2.28.0 will require again new code changes and at least the job is already done for v2.23.1. v2.23.1 bring new bugs fixed and that's something we welcome very much.

[Perflyst]

I guess we should use the liblsquic from https://github.com/iv-org/lsquic-static-alpine. Just opened iv-org/lsquic-static-alpine#1

[unixfox]

Sure if you create a new tag on https://github.com/iv-org/lsquic-static-alpine I can test on my instance.

[Perflyst]

You can get the build from the PR here: https://github.com/iv-org/lsquic-static-alpine/suites/1995406313/artifacts/39816860

[saltycrys]

iv-org/lsquic-static-alpine#1 had a wrong commit for BoringSSL, fixed in iv-org/lsquic-static-alpine#2.

Release available here: https://github.com/iv-org/lsquic-static-alpine/releases/tag/v2.23.1
liblsquic.a v2.23.1 available here: https://github.com/iv-org/lsquic-static-alpine/releases/download/v2.23.1/liblsquic.a

[Perflyst]

Patch is now in testing on my server

[Perflyst]

The patch is working fine for 3 days on one of my backend, I guess it's ready. Thanks again @vhuynh3000