-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Increase askpass timeout for git operations #42946
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hi @11happy and thanks! I think a better approach here might be to run git hooks in a separate step without the askpass delegate, so that they don't eat into the timeout if they run for a while. This is how I would approach it, just talking about the
|
|
FWIW @cole-miller and I have already implemented most of the machinery in #43285. All that's now left is to add |
Signed-off-by: 11happy <soni5happy@gmail.com>
Signed-off-by: 11happy <bhuminjaysoni@gmail.com>
Thank you for these pointers & work on |
Signed-off-by: 11happy <bhuminjaysoni@gmail.com>
|
corrected the error message! |
|
🥳 Thanks! Curious to see what you'll do next! |
|
Congrats on another great contribution @11happy !! |
This reverts commit a74aac8.
This reverts commit a74aac8. cc @11happy, we need to do a bit more than just running `git hook pre-push` before pushing, as described [here](#42946 (comment)). Right now this is also running the pre-push hook twice. Release Notes: - N/A
This reverts commit a74aac8. cc @11happy, we need to do a bit more than just running `git hook pre-push` before pushing, as described [here](#42946 (comment)). Right now this is also running the pre-push hook twice. Release Notes: - N/A
This reverts commit a74aac8. cc @11happy, we need to do a bit more than just running `git hook pre-push` before pushing, as described [here](#42946 (comment)). Right now this is also running the pre-push hook twice. Release Notes: - N/A
… (cherry-pick to preview) (#44583) Cherry-pick of #44578 to preview ---- This reverts commit a74aac8. cc @11happy, we need to do a bit more than just running `git hook pre-push` before pushing, as described [here](#42946 (comment)). Right now this is also running the pre-push hook twice. Release Notes: - N/A Co-authored-by: Cole Miller <cole@zed.dev>
… (cherry-pick to stable) (#44584) Cherry-pick of #44578 to stable ---- This reverts commit a74aac8. cc @11happy, we need to do a bit more than just running `git hook pre-push` before pushing, as described [here](#42946 (comment)). Right now this is also running the pre-push hook twice. Release Notes: - N/A Co-authored-by: Cole Miller <cole@zed.dev>
…2946)" (zed-industries#44578) This reverts commit a74aac8. cc @11happy, we need to do a bit more than just running `git hook pre-push` before pushing, as described [here](zed-industries#42946 (comment)). Right now this is also running the pre-push hook twice. Release Notes: - N/A
…2946)" (zed-industries#44578) This reverts commit a74aac8. cc @11happy, we need to do a bit more than just running `git hook pre-push` before pushing, as described [here](zed-industries#42946 (comment)). Right now this is also running the pre-push hook twice. Release Notes: - N/A
Closes zed-industries#29903 Release Notes: - Increased timeout from 17->300 & improved the error message. --------- Signed-off-by: 11happy <soni5happy@gmail.com> Signed-off-by: 11happy <bhuminjaysoni@gmail.com>
…2946)" (zed-industries#44578) This reverts commit a74aac8. cc @11happy, we need to do a bit more than just running `git hook pre-push` before pushing, as described [here](zed-industries#42946 (comment)). Right now this is also running the pre-push hook twice. Release Notes: - N/A
Closes #29903
Release Notes: