Hi ! I have an instance currently running on 2.9.0.beta4, and I needed to migrate it, so I did the basic backup/restore, but restore failed on the new instance. I decided then to try to update the original instance, but it failed also. Both failed, seemingly for the same reason, during the db:migrate command. Update error : https://pastebin.com/raw/sQrnMe27 Restore error : https://pastebin.com/raw/idWYmEFq Thanks for the help !

I think you should be able to run SiteSetting.selectable_avatars = "" (from the rails console again), and then be good for a rebuild.

Looks like it may be a :bug: This looks to me like it’s in core, but the standard question is Do you have any non-standard plugins?

No, it’s a vanilla one :slight_smile:

I had a similar error on my test site where I had some errant data in my selectable_avatar site setting, and had to update it through the rails console. Are you comfortable using the rails console? If so, could you run this and see what it says: SiteSetting.where(data_type:17)

I’m not sure if I’ve done it correctly, but here is what I get : => # ]>

Currently, rebuilding and just passed the stressful db migrate command, so I guess this one is fixed. Thank you both of you for your quick help !

Looks like you did it! You should see if you can get attention to this, as I’m pretty sure that migration is supposed to migrate those selectable avatars to the new format.

[image] Jay Pfaffman: that migration is supposed to migrate those selectable avatars to the new format. It is, and it’s worked in every other case we’ve seen. [] isn’t a valid value, even in the old format, so this particular case is quite surprising. Maybe it’s left over from some manual work on the console, or a bad import :thinking: If we get more reports, we’ll be sure to add an automated fix for this case.

[image] David Taylor: [] isn’t a valid value, Ah. Right. Usually when I get that error, it’s becuase I messed up such that I was accessing the wrong variable or something. But maybe that was the state that it was left in after all of the other ones had been deleted. But, really, I wasn’t paying close enough attention. :wink:

[image] Jay Pfaffman: But maybe that was the state that it was left in after all of the other ones had been deleted Our ‘list’ settings are a thin UI over pipe-delimited strings, so in theory an empty list should be stored as an empty string. But you make a good point - maybe someone was trying to empty the list and did something like this by accident: pry(main)> SiteSetting.selectable_avatars = [] => [] pry(main)> SiteSetting.selectable_avatars => "[]" (this is with the old format. The new format has validations to prevent this, even on the console)

[image] David Taylor: Maybe it’s left over from some manual work on the console, or a bad import Well in our case, the forum was set up at the beginning of this month, and no interactions with the console whatsoever (nor imports). In fact, I’ve discovered rails console today :smile:

Unable to restore/update discourse (PG::InvalidTextRepresentation: ERROR: invalid input syntax for type integer: "[]")

Product Support

Spitap June 13, 2022, 5:36pm 4

No, it’s a vanilla one

Topic		Replies	Views
Failed To Bootstrap Pups::ExecError 'bundle exec rake db:migrate' failed with return exec failed with the params 2.9.0.beta4 to 2.9.0.beta5 Self-hosting	6	1637	June 20, 2022
InvalidTextRepresentation: ERROR when trying to upgrade Product Support	11	3023	April 10, 2019
Database issues migrating form old version 20150822141540 Self-hosting	13	1297	September 22, 2022
Plugin causing errors during rebuild Self-hosting	20	2448	October 11, 2022
Cannot update with voting plugin Product Support	5	778	September 9, 2020

Unable to restore/update discourse (PG::InvalidTextRepresentation: ERROR: invalid input syntax for type integer: "[]")

Related topics