NPE when adding new registry in Quarkus CLI
See original GitHub issueDescribe the bug
When new registry is added into freshly installed Quarkus CLI, the operation fails with NullPointerException.
Expected behavior
New registry is added successfully.
Actual behavior
Exception in console:
java.lang.NullPointerException
at io.quarkus.registry.config.RegistriesConfigMapperHelper.serialize(RegistriesConfigMapperHelper.java:45)
at io.quarkus.registry.config.RegistriesConfig$Mutable.persist(RegistriesConfig.java:111)
at io.quarkus.cli.RegistryAddCommand.call(RegistryAddCommand.java:54)
at io.quarkus.cli.RegistryAddCommand.call(RegistryAddCommand.java:12)
at picocli.CommandLine.executeUserObject(CommandLine.java:1953)
at picocli.CommandLine.access$1300(CommandLine.java:145)
at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2358)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2352)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2314)
at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2179)
at picocli.CommandLine$RunLast.execute(CommandLine.java:2316)
at picocli.CommandLine.execute(CommandLine.java:2078)
at io.quarkus.cli.QuarkusCli.run(QuarkusCli.java:50)
at io.quarkus.cli.QuarkusCli_ClientProxy.run(Unknown Source)
at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:125)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:67)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:41)
at io.quarkus.cli.Main.main(Main.java:9)
How to Reproduce?
Steps to reproduce:
jbang app uninstall quarkus
rm -r ~/.quarkus/
jbang app install --fresh --force quarkus@quarkusio
$ quarkus version
2.6.1.Final # 2.5.2.Final worked as expected
quarkus registry add registry.quarkus.redhat.com
Output of uname -a
or ver
OS name: “linux”, version: “5.15.6-100.fc34.x86_64”
Output of java -version
11.0.13, vendor: Eclipse Adoptium
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of mvnw --version
or gradlew --version
)
No response
Additional information
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Quarkus Extension Registry
Quarkus Extension Registry ... The Quarkus dev tools, such as the Quarkus CLI, the Maven and the Gradle plugins, or code.quarkus.io can be...
Read more >Adding first registry in CLI erases the default one · Issue #21905
By default, registry list in CLI contains a default registry registry.quarkus.io and there is an option to add new registries.
Read more >Release Notes for Red Hat build of Quarkus 2.2
You can add metering labels to your Quarkus pods and check Red Hat ... For more information about custom registry configuration, ...
Read more >quarcus maven plugin fails to create a project - Stack Overflow
... [INFO] Your new application has been created in /Users/User/work/quarkus/test/createProject/getting-started [INFO] Navigate into this ...
Read more >2020 quarkus-fascicle-understanding-v1.pdf
More importantly, I am really happy when I hear users telling me how Quarkus has addressed their key Cloud Native needs and concerns:...
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
I have something building now
I did close it. I am trying to remove direct access to those Locators outside of the registry client package. Next thing on my list is making them package private. I can’t do it just yet because we still have the flying spaghetti monster in there running amok