Time to drop http-parser?

[utkarsh2102]

Hi,

http/http.gemspec

Line 33 in 8b432a7

gem.add_runtime_dependency "http-parser", "~> 1.2.0"

Can we patch http to not use http-parser because it looks like it is not being maintained actively; last commit was in October 2018.
Or is there any alternative that we could possibly use?

[ixti]

We had plans of switching to own ffi binding, but we don't have enough bandwidth to do so. Meanwhile, you should not worry about http-parser as long as it works fine.

[Jcambass]

We run into random segfaults when we upgraded from 4.1.1 to 4.4.1. After some digging we found that this was caused by the new Compacting GC in ruby 2.7 and the ffi library used by http-parser. ffi has already issued a fix for this.

For now we fixed this by manually including ffi 1.13.1 in our gemfile to include the fix. I also opened a PR to require at least ffi 1.13.1 for http-parser.

However, this still makes me wonder if this project should either bring it's own ffi binding (if there are resources) or maybe more realistic, try to take over (if really needed, fork) http-parser.