This is a rare bug, but it happens when a project that has evolved from at least one other project (name change, not phase1->phase2 type evolution) is created by calling Project::newFromId. It does not grab the latest version of that project, rather I think it is grabbing the version when the evolve change happened. A workaround that I am using right now is to call Project::newFromHistoricName after Project::newFromId, which seems to be working at least for all the cases that I have seen. In most cases this doesn't affect anything, however it can produce some weird/conflicting results when looking at the status of projects (in particular checking whether or not the project is deleted)
This is a rare bug, but it happens when a project that has evolved from at least one other project (name change, not phase1->phase2 type evolution) is created by calling Project::newFromId. It does not grab the latest version of that project, rather I think it is grabbing the version when the evolve change happened. A workaround that I am using right now is to call Project::newFromHistoricName after Project::newFromId, which seems to be working at least for all the cases that I have seen. In most cases this doesn't affect anything, however it can produce some weird/conflicting results when looking at the status of projects (in particular checking whether or not the project is deleted)