fwiw. We’ve updated to

v0.11.0

from

v0.10.4

without any issues. This is with a custom deployment setup on AWS ECS. One thing we are noticing is that our protobuf ingestion no longer shows the package structure of the datasets in the new navigation. Instead, all protobuf messages are listed at a top level and there is no way to filter them by their package folder, etc. Is this a change made as part of the browsepathv2 aspect?

@square-jordan-23985 Could you take a look at this?

Hello @average-vr-23088, could you share how you are doing the protobuff ingestion? I am looking into ways of doing the same.