com_github_fmtlib_fmt has a newer release 8.0.1

[ME-ON1]

WARNING com_github_fmtlib_fmt has a newer release than 7.0.3@<2020-08-07 13:39:57>:8.0.1@<2021-07-02 23:14:33>

[phlax]

@ME-ON1 does com_github_nodejs_http_parser have a newer release that we can use ?

other ci is flagging issues with it

[phlax]

/me wonders if you are [bot]

[phlax]

8/

[ME-ON1]

No i was working on this issue #16705 and was running script locally but it created issues.

[phlax]

cool, if you are looking to PR updates the one i posted needs looking at so i was watching you posting hoping it would appear 8/

i can look into it tho

[ME-ON1]

@ME-ON1 does com_github_nodejs_http_parser have a newer release that we can use ?

These are the logs coming from release_dates.py
Also have no knowledge about that. I'm new with code base here.

[phlax]

are you on slack ?

[ME-ON1]

Yes, with dogebinge name.

[moderation]

@ME-ON1 does com_github_nodejs_http_parser have a newer release that we can use ?

other ci is flagging issues with it

The latest release for nodejs/http-parser is a documentation change saying the project is deprecated 😞

We had a couple of folks try to get the replacement llhttp over the line and it looks close but not quite there yet - #15814. @asraa has been leading the charge.

[phlax]

not an easyfix it seems. Also that PR keeps the legacy parser initially so the problem wouldnt go away straight away

[asraa]

yeah, it's been blocked for a while -- handed off to some other Googlers. maybe @KBaichoo knows the status? I'm not 100% sure who was taking it over...

[KBaichoo]

We (me and @yanavlasov) haven't yet started digging into the llhttp yet, but are planning on working on it. There are a few open questions on how debuggable llhttp is given it's transpiled to C, and how patching it could work.

[phlax]

closing this as there is a newer ticket for it #18321