Clone repo for first time, running runZap outputs errors but still works
See original GitHub issueI tried seeing what it would be like for a first time user to clone the repo and try to run the HUD with the ./gradlew runZap
command. It took about 3 minutes to execute, and ultimately worked perfectly. But when the gradle CLI finished up it reported errors.
I’m curious about why it reported errors but still worked. This may be confusing to first time users.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
The remote end hung up unexpectedly while git cloning
My git client repeatedly fails with the following error after trying to clone the repository for some time.
Read more >Fix Git's 'fatal: repository not found' error quickly | TechTarget
Here are five ways to fix that problem and successfully clone, ... only to run head first into Git's 'fatal: repository not found'...
Read more >Git error - Fatal: Not a git repository and how to fix it | Datree.io
This error means you attempted to run a Git command, but weren't inside a Git repository. Make sure you've: Navigated to the right...
Read more >Pipeline options for Git repositories - Azure - Microsoft Learn
In this article. Branch; Clean the local repo on the agent; Label sources; Report build status (Azure Pipelines, TFS 2018 and newer); Checkout ......
Read more >git - Can't clone remote repository - Visual Studio Feedback
I'm able to clone the repository using Visual Studio 2013 and/or by ... Git Output window: Error encountered while cloning the remote repository:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just a config, it enables heap dumps when the Java process hits an OutOfMemoryError (if you were referring to that?).
Yes, the 20s start counting just after starting the ZAP process.
Regarding the previous comment, that’s Gradle daemon process: https://docs.gradle.org/current/userguide/gradle_daemon.html