Initially reported in Q272 by @linan

The original report in Q272 is almost certainly unrelated.

Do you have a specific set of reproduction steps I can take against a local install to demonstrate this issue? This report seems to have a lot of observations but I don't understand what the reproduction steps are. See Contributing Bug Reports.

I wish I could reproduce it.
But all new projects I create work perfectly fine.

It seems to only be affecting projects prior to an upgrade done last week.(Jan 4th).

Prior to T9551 (circa October 12), projects could generate with invalid hashtags, but I don't think these ever worked (at least, many of them definitely did not work).

You should be able to force generation of new hashtags by changing the name of the project (then, presumably, changing it back).

Actually changing it back is failing with

error #1406: Data too long for column 'slug' at row 1

When I change
NZ COR - NZ/FM Integration
to
NZ COR: NZ/FM Integration

Can you show me the output of bin/storage adjust? (For now, decline to apply any changes it suggests.)

/var/www/phabricator# bin/storage adjust
Verifying database schemata...
Found no adjustments for schemata.

I'm not really sure what's going on. The limit on the slug column is 128 characters, and that project name is nowhere near that (we should raise a better error message than we do, but I'm not sure how you're hitting the issue in the first place).

I can create projects with either name locally without issues:

Do you have a value in the "Additional Hashtags" field (or showing in "Hashtags" on the project detail page) which is ridiculously long?

Yes..
nz_cor:_nz_fm_integrationnz_cor_nz_fm_integrationnz_cor_nz_fm_integrationnz_cor_-_nz_fm_integrationnz_cor_nz_fm_integrationnz_cor_nz_fm_integration
Is in there now.
I'll remove those.

Removing those allowed me to save.

404's continue.