Upgrade hyper to 1.0
Renovate has created the base PR which doesn't pass the CI checks.
https://github.com/tailcallhq/tailcall/pull/636
Technical Requirements
- Hyper version for both server should be updated to 1.0
- No performance degradation should be observed
- No tests should fail or require modification
/bounty 120$
💎 $120 bounty • Tailcall Inc.
Steps to solve:
- Start working: Comment
/attempt #650with your implementation plan - Submit work: Create a pull request including
/claim #650in the PR body to claim the bounty - Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts
🙏 Thank you for contributing to tailcallhq/tailcall! 🧐 Checkout our guidelines before you get started. 💵 More about our bounty program.
| Attempt | Started (GMT+0) | Solution |
|---|---|---|
| 🔴 @varshith257 | May 14, 2024, 10:47:13 PM | WIP |
| 🟢 @ssddOnTop | #2013 |
Can you assign this to me
@tusharmath I’ve not got any new tickets in a bit 🙌
Can I be assigned to this ?
@tusharmath I request you to assign this to me.
I have done some digging into the issue why the compilation is issue.
I think you should put this to hold because of two reasons.
- We heavily depend on
hyperandreqwest hyperandreqwestare co-related here in this context thusreqwestalso should be updated according to the version ofhyperdue to mis-matching type definitions.
We should wait till reqwest get's same version update that matches with hypers latest version (reqwest is going to be breaking change)
more on this https://github.com/seanmonstar/reqwest/issues/2039
Thanks @b4s36t4 .
@ayewo let me keep this unassigned until reqwest also upgrades.
Action required: Issue inactive for 30 days. Status update or closure in 7 days.
I won't be attempting this issue again.. for anyone who picks this up, you can refer to my previous PRs on how I handled requests (because hyper::Body is a trait now).