Just a quick little patch for some chargen issues introduced in V0.48.
1 Like
I never saw one like this before. They were using: scene/location 670=Bay/Two If By Sea
2019-05-14 22:01:31 ERROR - Error in scene/location 670=Bay/Two If By Sea: client=2377 error=missing interpolation argument :description in “Scene location changed:%R%R%{description}” ({:name=>“Justin”, :location=>“Bay/Two If By Sea”} given) backtrace=["/home/ares/.rvm/gems/ruby-2.6.0/gems/i18n-0.9.5/lib/i18n/config.rb:97:in block in missing_interpolation_argument_handler'", "/home/ares/.rvm/gems/ruby-2.6.0/gems/i18n-0.9.5/lib/i18n/interpolate/ruby.rb:29:inblock in interpolate_hash’", “/home/ares/.rvm/gems/ruby-2.6.0/gems/i18n-0.9.5/lib/i18n/interpolate/ruby.rb:21:in gsub'", "/home/ares/.rvm/gems/ruby-2.6.0/gems/i18n-0.9.5/lib/i18n/interpolate/ruby.rb:21:ininterpolate_hash’”, “/home/ares/.rvm/gems/ruby-2.6.0/gems/i18n-0.9.5/lib/i18n/interpolate/ruby.rb:17:in interpolate'", "/home/ares/.rvm/gems/ruby-2.6.0/gems/i18n-0.9.5/lib/i18n/backend/base.rb:175:ininterpolate’”, “/home/ares/.rvm/gems/ruby-2.6.0/gems/i18n-0.9.5/lib/i18n/backend/base.rb:58:in translate'", "/home/ares/.rvm/gems/ruby-2.6.0/gems/i18n-0.9.5/lib/i18n/backend/fallbacks.rb:47:inblock (2 levels) in translate’”, “/home/ares/.rvm/gems/ruby-2.6.0/gems/i18n-0.9.5/lib/i18n/backend/fallbacks.rb:46:in catch'", "/home/ares/.rvm/gems/ruby-2.6.0/gems/i18n-0.9.5/lib/i18n/backend/fallbacks.rb:46:inblock in translate’”]
1 Like
I think you might have a merge conflict, because that message no longer appears in the current version.
In 0.47 it was (in scenes locale_en.yml):
location_set: "Scene location changed:%R%R%{description}"
In 0.49 it’s now:
location_set: "%{name} changed the scene location to %{location}."
So your old version is expecting a description, which is not being passed in the new version (because it isn’t used any more).
1 Like
Thank you kindly! <3
Just checking the error log for Cupcake’s issues (see MSB), I noticed these:
2019-05-15 10:08:58 ERROR - Web client error: a glimmer transaction was begun, but one already exists. You may have a nested transaction : undefined.
2019-05-15 10:08:58 ERROR - Web client error: Object doesn't support property or method 'includes' : undefined.
No one (other than Cupcake) has reported any errors, and everything is working fine for me.
Thanks. I’d need a little more context in terms of when that error happened to figure out what went wrong. There’s no stack trace or anything? If it’s not spamming the error log, though, it seems that it would be a specific bug on a specific page, and not something site-wide.
Re: the above - this seems to be creating no particular issues. I still see it, but there’s no pattern, so I am assuming it is a specific page. I’m still combing through to see if it’s anything I did (because it probably is).
This is unrelated, and it seems like it’s not a big deal.
%% Channel roles updated.
[RP Requests] KarmaBum has changed the permissions on this channel.
[RP Requests] has left this channel.
[RP Requests] has left this channel.
[RP Requests] has left this channel.
[RP Requests] has left this channel.
[RP Requests] has left this channel.
[RP Requests] has left this channel.
[RP Requests] has left this channel.
[RP Requests] has left this channel.
No errors or anything. I assume all those are people I’ve nuked (since I nuke them if they get approved then never RP). Just thought I’d mention it as a thing I noticed.
1 Like
Thanks. I guess I’m not removing them from the channels when they’re nuked. This may have created zombie characters, which can gum up other commands. You can find out if you have zombie chars by doing ruby Character.all.select { |c| !c.name }.map { |c| c.id } to get their IDs. That’ll find anybody without a name, which is the indication for a zombie char that was nuked but got accidentally half-resurrected by bad code 
1 Like
[]
%% Done!
Zombie-free, TY! 
1 Like