Is there a reason that we can鈥檛 delete or at least hide the default project in phoenix? We have discrete project names for every deployment and the default sits empty but unable to be removed
馃挕聽Hint: Mention RunLLM in the thread for followups.
Hey Ben M. - it's sorta historical but also intentional for a few reasons. Any trace that doesn't have a project in the resource ends up in the default project. Often times people forget to add this and then go searching for the trace, only to find it in the default. Since we dynamically create projects, if we allowed it to be deleted, it would keep regenerating, causing a bit of thrash. We also allow for project switching at runtime in notebooks using a context manager (e.g. using_project ) - We did this for experimentation reasons but it has some caviots in that spans could escape the context manager if they happened in things like threads or background processes. To be able to ensure that a span always landed in a project and then could be re-constructed I believe is why we made it un-deletable. I believe those were the reasons 馃槄 Happy to explore making it deletable 馃し
It's not the end of the world, we just have a perpetually empty project in production 馃槃 Another option would be renaming it, but either way this is a low low priority IMO
Gotcha, well lmk if it gets really annoying 馃檪
