anchor.diff:  
   ==== Permission denied
   
  -If you get "permission denied", that means that Gradle likely exists in the correct place, but it is not executable. You can fix this using `chmod +x path/to/executable` on *nix-based systems.
  +If you get "permission denied", that means that Gradle likely exists in the correct place, but it is not executable.
  +You can fix this using `chmod +x path/to/executable` on *nix-based systems.
   
   ==== Other installation failures
   
  
positive.code: You can learn what the task outcomes mean from <<sec:task_outcomes,this listing>>.
  
  
  === Debugging IDE integration
  
  Many infrequent errors within IDEs can be solved by "refreshing" Gradle. See also more documentation on working with Gradle link:https://www.jetbrains.com/help/idea/gradle.html[in IntelliJ IDEA] and link:http://www.vogella.com/tutorials/EclipseGradle/article.html[in Eclipse].
  
  ==== Refreshing IntelliJ IDEA
  
  
negative.code: 
  The link:https://scans.gradle.com/s/sample/troubleshooting-userguide/dependencies?expandAll&filters=WzFd&toggled=W1swXSxbMF0sWzAsMF0sWzAsMV1d[actual build scan] with filtering criteria is available for exploration.
  
  [[sec:troubleshooting_performance]]
  === Troubleshooting slow Gradle builds
  
  For build performance issues (including “slow sync time”), see the guide to link:https://guides.gradle.org/performance/[Improving the Performance of Gradle Builds].
  
  Android developers should watch a presentation by the Android SDK Tools team about link:https://youtu.be/7ll-rkLCtyk[Speeding Up Your Android Gradle Builds].
  Many tips are also covered in the Android Studio user guide link:https://developer.android.com/studio/build/optimize-your-build.html[on optimizing build speed].
  
  [[sec:troubleshooting_build_logic]]
  === Debugging build logic
  
  ==== Attaching a debugger to your build
  