Getting Error after Running Prepare Manifest

No-Code Platform
1

I am encountering this error after running Prepare Manifest on my Merge Request:

{
“Message”: “Cannot invoke “net.nextworld.metadata.catalog.MetadataTypeInfo.getUniqueKeys()” because “typeInfo” is null”,
“Stack Trace”: [
“java.lang.NullPointerException: Cannot invoke “net.nextworld.metadata.catalog.MetadataTypeInfo.getUniqueKeys()” because “typeInfo” is null”,
“at net.nextworld.patching.manifests.initialization.detailproviders.FamilyDetailProvider.buildManifestDetail(FamilyDetailProvider.java:217)”,
“at net.nextworld.patching.manifests.initialization.detailproviders.ManifestObjectHandler.getManifestDetail(ManifestObjectHandler.java:45)”,
“at net.nextworld.patching.manifests.initialization.detailproviders.DefaultObjectHandler.get(DefaultObjectHandler.java:39)”,
“at net.nextworld.patching.manifests.initialization.detailproviders.MergeRequestDetailProvider.lambda$buildAndProcessManifestDetails$1(MergeRequestDetailProvider.java:129)”,
“at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)”,
“at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1708)”,
“at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)”,
“at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:276)”,
“at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1708)”,
“at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)”,
“at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)”,
“at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)”,
“at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)”,
“at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)”,
“at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)”,
“at net.nextworld.patching.manifests.initialization.detailproviders.MergeRequestDetailProvider.buildAndProcessManifestDetails(MergeRequestDetailProvider.java:148)”,
“at net.nextworld.patching.manifests.initialization.ManifestInitializer.initialize(ManifestInitializer.java:132)”,
“at net.nextworld.patching.manifests.initialization.ManifestInitializer.execute(ManifestInitializer.java:91)”,
“at net.nextworld.dataaccess.logicblocks.executor.LogicBlockRunner.run(LogicBlockRunner.java:143)”,
“at io.opentelemetry.context.Context.lambda$wrap$1(Context.java:212)”,
“at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)”,
“at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)”,
“at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)”,
“at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)”,
“at java.base/java.lang.Thread.run(Thread.java:1583)”
]
}

Anyone knows what might be the issue?

2

That looks like a bug.

If you are a Nextworld customer or partner, work with your system administrator to submit a ticket with customer support, who will file a bug on your behalf. Include a link to this post in the ticket. If you’re not a Nextworld customer, keep an eye on release notes. We’re always making improvements.

3

Someone mentioned that we can’t include Endpoint Response Codes. Maybe that is the reason? Can we include Endpoint Config and Endpoint Response though?

4

Is this issue because Endpoint Response Codes are not lifecycle aware and therefore cannot be added to a manifest? Agreed that this feels like a bug because manifests should skip non-lifecycle objects instead of failing.

Endpoint Definitions and Endpoint Response Set Definitions also are not lifecycle aware, so these may run into the same manifest issues. If you are working with your administrator to submit a ticket, please include information about these as well if they are at issue.

1 Like
5

That sounds likely but we can’t know for sure until we delve into the bug. These NullPointerExceptions are not informative enough and always require some debugging to determine. You can try excluding your Response Codes and seeing if that gets you past the error. Response Codes are not in our collection of supported metadata types, so it’s a believable theory.

These are supported metadata types and should be valid for inclusion in a metadata manifest.

1 Like
6

NullPointerException s are always bugs, regardless of the expected manifest/lifecycle behavior.

3 Likes
7

Okay, after including only the base Endpoint Config and Endpoint Response objects (i.e. removing all the base Endpoint Response Codes) in a new merge request, I was able to prepare manifest now. As suggested, I already opened a support ticket. Thanks for your help.

2 Likes