-
Notifications
You must be signed in to change notification settings - Fork 275
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
Failed to apply plugin org.jetbrains.intellij
: getHeaderField("Location") must not be null
#960
Comments
Looks like an issue with networking. Do you have an access to GitHub on the environment from which you run the project? |
No, I can't access to GitHub. |
This seems to be a check for the latest version, how can I skip this step? |
As for now, you may put Gradle in offline mode. |
Ok, Thanks. |
代理断线,换一个节点 |
@mdddj Please use English. |
@hsz I have the same issue in my environment: no access to github. Using 1.5.2 for now. When is this new release happening ? |
This looks like a network problem, replacing a good network solved my problem |
The issue in my case is the corporate environment having firewall rules for security reasons. This is not something that can be changed unfortunately |
A quick fix here would be to simply throw an exception with a better error message, to tell the user to use |
A quick fix here would be to simply throw an exception with a better error message, to tell the user to use |
1 similar comment
A quick fix here would be to simply throw an exception with a better error message, to tell the user to use |
A quick fix here would be to simply throw an exception with a better error message, to tell the user to use |
Gradle plugin portal was having some issues lately, so it could still be networking related. |
@yangyang5214 please update to latest release of the plugin |
https://github.com/yangyang5214/teemo/blob/feature/transform_plugin/build.gradle.kts#LL3C23-L3C23 The bug still exists, is the latest version v1.14.1. (My working env is intranet. so use offline compilation, this's ok) |
This issue occurred again but in a different place this time. It turned out that Gradle's
can lead to the same exception. Anyways, fixed with e001629 — will be released with |
The text was updated successfully, but these errors were encountered: