tailcall

tailcall copied to clipboard

The debug build time for tailcall is fairly high. This issue targets improving the clean build time for the project by 70%.

/bounty 200$

~~## 💎 $200 bounty • Tailcall Inc.~~

~~### Steps to solve:~~ ~~1. Start working: Comment /attempt #831 with your implementation plan~~ ~~2. Submit work: Create a pull request including /claim #831 in the PR body to claim the bounty~~ ~~3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts~~

~~### Additional opportunities:~~ ~~* 🔴 Livestream on Algora TV while solving this bounty & earn $200 upon merge! Make sure to have your camera and microphone on. Comment /livestream once live~~

~~🙏 Thank you for contributing to tailcallhq/tailcall!~~ ~~🧐 Checkout our guidelines before you get started.~~

Attempt	Started (GMT+0)	Solution
🔴 @neo773	Dec 29, 2023, 7:47:11 AM	WIP
🟢 @ologbonowiwi	Feb 5, 2024, 6:51:38 PM	WIP

/attempt #831

@neo773: The Tailcall Inc. team prefers to assign a single contributor to the issue rather than let anyone attempt it right away. We recommend waiting for a confirmation from a member before getting started.

@tusharmath Seems like the conversation got lost in Discord reposting it here

Fantastic, raise a PR ill have a look

Hey @neo773, you still working on this?

@ologbonowiwi Nope

/attempt #831

@ologbonowiwi: Another person is already attempting this issue. Please don't start working on this issue unless you were explicitly asked to do so.

Action required: Issue inactive for 30 days. Status update or closure in 7 days.

@neo773 did you make any progress on this? I remember you posted something on discord, but didn't create PR.

@tusharmath Yes, the approach required upfront tooling installed (sccache) you can’t put it in cargo.toml as it requires exposing the path along with some of other variables and also takes a while to install.

@tusharmath Yes, the approach required upfront tooling installed (sccache) you can’t put it in cargo.toml as it requires exposing the path along with some of other variables and also takes a while to install.

Does this render the solution ineffective? There is no mention of whether the build times in question are in CI or local debug builds, quite a difference between the two.

There is no mention of whether the build times in question are in CI or local debug builds

As the issue's description mentions

The debug build time for tailcall is fairly high. This issue targets improving the clean build time for the project by 70%.

From our understanding so far the issue was aiming to solve local builds, but I hit the same wall as @neo773, most solutions found to improve build time require some sort of cache in a build that was done before, which require tooling to be installed on the contributor's machine.

If such solution is the expected, I'll be happy to open a PR; I have some code locally already

Action required: Issue inactive for 30 days. Status update or closure in 7 days.

Issue closed after 7 days of inactivity.