Where have the custom emojis gone?
-
@DoctorJones
I watched those arrows turn into
-
-
You must be using zoom > 100% - have you asked Blakey if he's seeing these problems as well?
-
@PJH said:
You must be using zoom > 100% - have you asked Blakey if he's seeing these problems as well?
When I zoom in I can see that emoji otherwise no!
-
@PJH said:
You must be using zoom > 100% - have you asked Blakey if he's seeing these problems as well?
I tried using zoom but all I can see is giant text everywhere. Thanks for nothing!!!
-
@DoctorJones
Did you try rebooting?
-
@Luhmann said:
Did you try rebooting?
I don't understand how a reboot could fix it, but I'll give it a shot... Be right back.
-
maybe it wasn't the reboot but the updates I installed?
Can you try and run windows updates?
-
Ok, I know you're all having fun, but time to crash the party.
This is probably because there are 4 instances of NodeJS running and you get assigned one of them based on your IP address. Somehow, one of them forgot how to emoji or something.
-
@ben_lubar said:
Ok, I know you're all having fun, but time to crash the party.
This is probably because there are 4 instances of NodeJS running and you get assigned one of them based on your IP address. Somehow, one of them forgot how to emoji or something.
Thanks for the info Ben, it looks like I got the retarded younger brother of the other instances.
-
@ben_lubar
So rebooting did fix it!(by connecting me to a working version)
-
-
@DoctorJones
though luck!
-
-
@Luhmann said:
So rebooting did fix it!
(by connecting me to a working version)
It connected you to the Discourse instance?
-
@ben_lubar Damn it, I told you JS cannot into multithread! See what you did? SEE?
Seriously though, is there a way for us to somehow check which instance we are connected to in case this kind of weird problems happen in the future? Might help us debug things.
-
@Onyx I've added an
X-Upstream
header to nginx. For example, I have this:X-Upstream: unix:/usr/share/nginx/wtdwtf-nodebb.sock/sock0
Which means I'm on the one true NodeBB instance.
-
@boomzilla said:
the emojis render correctly as images for me
They rendered as images, but stretched horizontally, for me. Refresh, and they're normal. Last night I was seeing text instead of images. It's discoursistent.
-
@ben_lubar I noticed the box I was connected to went down. I assume someone cycled it. Now it's back up, emojis are working again.
Thanks for the help.
FYI, I am currently on
X-Upstream:unix:/usr/share/nginx/wtdwtf-nodebb.sock/sock2
-
@ben_lubar said:
there are 4 instances of NodeJS running
NodeJS running NodeBB? Because I know that self-hosted iframely runs in node.
-
@boomzilla Yeah, four NodeBB's. But if I said "we're running four instances of NodeBB" people would get more confused.
-
@boomzilla said:
@Maciejasjmj Have you been playing with the new "view raw" stuff?
What's this "view raw" thing everyone keeps talking about?
-
WHERE IS MY HAPPY NAZI?
-
@Lorne-Kates Seems to have become more Aryan.
-
@ben_lubar it's happening again. Can you please take that "special" NodeBB instance out back and shoot it?
-
@DoctorJones
Can't it just go and tend the wabbits?
-
@Luhmann it can do whatever it likes as long as it doesn't do NodeBB any more.
-
@ben_lubar said:
This is probably because there are 4 instances of NodeJS running and you get assigned one of them based on your IP address. Somehow, one of them forgot how to emoji or something.
It might be a bug in the reload code.
-
@DoctorJones I just connected directly to each of the 4 instances and none of them had missing emoji. Next time you see that happen, can you grab the X-Upstream header from a computer on the same public IP?
-
@ben_lubar said:
Next time you see that happen, can you tattle on which instance is screwing with you?
I guess it's too much to look through the access logs? Or are they not a thing anymore?
-
@ben_lubar said:
Next time you see that happen, can you grab the X-Upstream header from a computer on the same public IP?
OK, I'll let you know
-
@loopback0 said:
@Lorne-Kates Seems to have become more Aryan.
Yeah, but she seems more like the disinterested daughter of some Nazi keener.
- meh whatever dad sieg meh
-
-
-
X-Upstream: unix:/usr/share/nginx/wtdwtf-nodebb.sock/sock1
-
Last restart appears to have caused custom emoji to disappear on me again. Not sure if anyone else is affected.
Same X-Upstream header.
-
@ChaosTheEternal that's because my pull request (which was previously applied locally) was accepted: https://github.com/NodeBB-Community/nodebb-plugin-emoji-static/pull/1
-
Some of those are nigh invisible when using a theme with a dark background:
.Is it possible to add a light outline or something to those? I assume most, if not all
fa_*
are affected.Paging @ben_lubar
-
@OffByOne said:
Some of those are nigh invisible when using a theme with a dark background:
.Is it possible to add a light outline or something to those? I assume most, if not all
fa_*
are affected.Paging @ben_lubar
I think that's the point of
-
@aliceif Head desk looks much less like a Doctor Who robotic cat on NodeBB.
-
Referencing @PJH's test at https://what.thedailywtf.com/topic/17178/spin-o-rama/2
:boat: :car: :facepunch: :flipper: :hand: :hash: :heavy_exclamation_mark: :hocho: :lantern: :large_blue_circle: :moon: :phone: :running: :shoe: :tshirt: :uk:
-
@Tsaukpaetra most of the missing ones are related to this bug:
-
@Tsaukpaetra That's so cool! They stream and reflow one at a time, sliding across the screen beautifully!
...it probably shouldn't do that.
-
@Magus said in Where have the custom emojis gone?:
That's so cool! They stream and reflow one at a time, sliding across the screen beautifully!
But only once! Once it's in the cache, it goes way too quickly to enjoy anymore...
-
@Magus Well, they could maybe assume that all emoji are 20x20...
And then some bastards come along and add to the set...
-
This post is deleted!
-
@Onyx Or maybe .
Or
-
@abarker Wait a second โฆ
is tiny! It appears that instead of assuming that all emoji should be 20ร20, NodeBB assumes that all emoji should be 20px tall.
This needs fixing.
-
-
@DoctorJones i see them too. (well badly, I'm on the dark theme)
Have you tried a hard refresh?