At the time we were adding the new sidebar (https://github.com/wandb/core/pull/20661/) we also added redirecting of the /entity/project page to the traces page when the project has Weave data and no Models data.
Browse3 has similar redirection code, taking you from /entity/project/weave to the traces page.
In its current state, the code always redirects you to the traces page. It was doing a query to see if the project has published data and showing a loader, but this is unnecessary if we're going to redirect regardless of the result.
The query is particularly bad because the limit parameter to useRootObjectVersions does not get passed along and used as it should, so it is fetching all of the object information for the project even though we only cared about a non-zero count.
At the time we were adding the new sidebar (https://github.com/wandb/core/pull/20661/) we also added redirecting of the
/entity/project
page to the traces page when the project has Weave data and no Models data.Browse3 has similar redirection code, taking you from
/entity/project/weave
to the traces page.In its current state, the code always redirects you to the traces page. It was doing a query to see if the project has published data and showing a loader, but this is unnecessary if we're going to redirect regardless of the result.
The query is particularly bad because the limit parameter to useRootObjectVersions does not get passed along and used as it should, so it is fetching all of the object information for the project even though we only cared about a non-zero count.