I feel like I accidentally broke GtS on my end lmfao

(setting the display name to "undefined" may have been a mistake)

edit: eyup, doing surgery on a database to change my display name away from "undefined" helped

@awoo@gts.apicrim.es what the hell, how would that break it? Is it evaling strings or something??? ​​

@awoo@gts.apicrim.es what the hell, how would that break it? Is it evaling strings or something??? ​​

@hazelnoot@enby.life @awoo@gts.apicrim.es does gts use an orm? if it does that might be a reason.

uhh, @dumpsterqueer, I think I found another bug in GtS lol

@awoo go on?

@dumpsterqueer so, changing one's display name to undefined doesn't let one change it to anything else because it then just... fails? no idea what exactly happens, but it required poking at the database to fix it.

@awoo what fails exactly? logs etc?

@dumpsterqueer let me spin up a testrig-

@awoo just did it myself + changed a display name to undefined and I don't see anything weird

@dumpsterqueer is it something on my end then that makes it weird? since the request times out and it then leaves me stuck with that display name.

@dumpsterqueer if it helps, the database is a postgresql one.

@awoo alright, just tried it on Postgres, GtS v0.20.2, and it seems fine there too