Hi all! I'm trying to modify the Container entity by creating custom aspects. However, Docker is throwing this error, and my custom aspects are not loaded. Any help or insight would be greatly appreciated, thanks!

15:58:40.956 [pool-3-thread-1] ERROR c.l.m.m.r.PluginEntityRegistryLoader:182 - Tried 5 times. Failed to load registry mycompany-cl-model with java.lang.UnsupportedOperationException: Failed to find Snapshot associated with Config-based Entity

at com.linkedin.metadata.models.ConfigEntitySpec.getSnapshotSchema(ConfigEntitySpec.java:73)

at com.linkedin.metadata.models.registry.MergedEntityRegistry.mergeEntitySpecs(MergedEntityRegistry.java:110)

at com.linkedin.metadata.models.registry.MergedEntityRegistry.apply(MergedEntityRegistry.java:59)

at com.linkedin.metadata.models.registry.PluginEntityRegistryLoader.loadOneRegistry(PluginEntityRegistryLoader.java:147)

at com.linkedin.metadata.models.registry.PluginEntityRegistryLoader.lambda$null$5(PluginEntityRegistryLoader.java:100)

at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)

at com.linkedin.metadata.models.registry.PluginEntityRegistryLoader.lambda$start$6(PluginEntityRegistryLoader.java:100)

at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)

at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)

at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)

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.lang.Thread.run(Thread.java:829)

Hi Samantha, could you follow the steps here and let me know if you get any unexpected errors? https://datahubproject.io/docs/debugging

When I run

datahub docker check

I get this error:

UnicodeEncodeError: 'charmap' codec can't encode character '\u2714' in position 0: character maps to <undefined>

[2022-11-23 08:46:50,227] ERROR    {datahub.entrypoints:195} - Command failed:

'charmap' codec can't encode character '\u2714' in position 0: character maps to <undefined>.

I also get this error when I quickstart, but datahub still launches and functions locally.

Interesting! And you are sill having the initial problem as well?

Yes, when I try to insert data into the custom aspect that I created, it will say that there is no such aspect. Looking into the docker logs, it looks like the custom aspect is getting discovered and added, before it suddenly fails and reattempts

13:46:16.562 [pool-3-thread-1] WARN  c.l.m.m.r.PluginEntityRegistryLoader:185 - Attempt 2 to re-load registry mycompany-cl-model: 0.0.2-dev

13:46:16.568 [pool-3-thread-1] INFO  c.l.m.m.r.PluginEntityRegistryLoader:139 - com.linkedin.metadata.models.registry.PluginEntityRegistryLoader@6bd22879: Registry mycompany-cl-model:0.0.2-dev discovered. Loading...

13:46:16.572 [pool-3-thread-1] INFO  c.l.m.m.registry.PatchEntityRegistry:104 - Loading custom config entity file: /etc/datahub/plugins/models/mycompany-cl-model/0.0.2-dev/entity-registry.yaml, dir: /etc/datahub/plugins/models/mycompany-cl-model/0.0.2-dev

13:46:16.572 [pool-3-thread-1] INFO  c.l.m.m.registry.PatchEntityRegistry:104 - Loading custom config entity file: /etc/datahub/plugins/models/mycompany-cl-model/0.0.2-dev/entity-registry.yaml, dir: /etc/datahub/plugins/models/mycompany-cl-model/0.0.2-dev

13:46:28.275 [pool-3-thread-1] INFO  c.l.m.m.registry.PatchEntityRegistry:141 - Discovered entity container with aspects testAspect

13:46:28.275 [pool-3-thread-1] INFO  c.l.m.m.registry.PatchEntityRegistry:141 - Discovered entity container with aspects testAspect

13:46:28.276 [pool-3-thread-1] INFO  c.l.m.m.registry.PatchEntityRegistry:152 - Adding aspect testAspect with spec com.linkedin.metadata.models.AspectSpec@6b62243c

13:46:28.276 [pool-3-thread-1] INFO  c.l.m.m.registry.PatchEntityRegistry:152 - Adding aspect testAspect with spec com.linkedin.metadata.models.AspectSpec@6b62243c

13:46:28.282 [pool-3-thread-1] WARN  c.l.m.m.r.PluginEntityRegistryLoader:185 - Attempt 3 to re-load registry mycompany-cl-model: 0.0.2-dev

13:46:28.288 [pool-3-thread-1] INFO  c.l.m.m.r.PluginEntityRegistryLoader:139 - com.linkedin.metadata.models.registry.PluginEntityRegistryLoader@6bd22879: Registry mycompany-cl-model:0.0.2-dev discovered. Loading...

Hi @ancient-library-85500, it seems like this could be a conflict or bug, could you submit an issue on github?