Null chars in config file causing IllegalArgumentException: URI can't be null
See original GitHub issuejava.lang.IllegalArgumentException: URI can't be null.
at java.base/sun.net.spi.DefaultProxySelector.select(DefaultProxySelector.java:163)
at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1181)
at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1081)
at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:189)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1592)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1520)
at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:250)
at com.wakatime.intellij.plugin.Dependencies.downloadFile(Dependencies.java:266)
at com.wakatime.intellij.plugin.Dependencies.installCLI(Dependencies.java:178)
at com.wakatime.intellij.plugin.WakaTime$1.run(WakaTime.java:112)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:263)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:668)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:665)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:665)
at java.base/java.lang.Thread.run(Thread.java:829)
Using CLion 2021.2, only had this issue after the latest update.
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
java.lang.IllegalArgumentException: Pattern cannot be null or ...
1 Answer 1 ... Within your security configuration, you are using a property placeholder that do not have a matching value in your...
Read more >ContentResolver | Android Developers
Note: passing a null context here could lead to unexpected behavior in certain ContentResolver ... Open a raw file descriptor to access data...
Read more >Bug Patterns - Error Prone
This value cannot be null, and comparing it to null may be misleading. ProtoStringFieldReferenceEquality. Comparing protobuf fields of type String using ...
Read more >WebLogic Server Known and Resolved Issues
If you deploy a web app as an archive war file, then context.getRealPath() returns null. This behavior can lead to certain failures in...
Read more >MyBatis 3 | Configuration
Specifies the JDBC type for null values when no specific JDBC type was provided for the parameter. Some drivers require specifying the column ......
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
Fixed in v13.1.8 released today.
I poked around a bit more, opened up
~/.wakatime-internal.cfg
and saw about 2kb of null characters in the file on the cli_version field. Removed them and the issue is now gone. Not sure how they got there in the first place, but thanks for helping figure this out! If there’s anything else lmk