If it helps I can upload the original uncompressed image so someone could look at both.
Although, since I could repo on our instance of nodebb over at plutonium with both the compressed and uncompressed image, the bug seems to be caused by something unrelated to the compression itself

Thank you, it's always a pleasure to report bugs on this community since they get addressed incredibly fast.
Cheers

Hello, I am getting the following bug on our instance of nodebb @ plutonium.pw

The repo steps are the following:

• As a forum moderator with enough privileges, find the user you want to change the profile picture of
• Upload a new profile picture on the user's profile
• Observe the user's profile picture change alongside yours (the moderator) on the top-right side banner on your screen

PICTURES

Before:

After:

What happened?
The pictures show the user in the "before" having the default forum profile picture we set up on our website which is meant to look like an atom.
On the top right of the screen, you see my profile picture which is different from that.
After I uploaded a new profile picture both the user and mine changed to the user's new profile picture.

Please note that the bug appears to be purely "visual" as it does not actually change my profile picture although it looks like it.
A simple page refresh clears out the wrong profile picture from my banner on the top right side of my screen.

If you wish, I can also upload a video showcasing the repro steps, I just thought pictures were simpler.

I kindly ask a moderator of this community to try to reproduce this on an unsuspecting user like myself (like changing my profile picture to something else) and see if the same visual glitch can be reproduced on your side.

Details:
NodeBB version
v3.3.6

NodeBB git hash
7fb3879

NodeJS version
v18.16.0

Installed NodeBB plugins
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, disabled)
[email protected] (installed, disabled)
[email protected] (installed, disabled)
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, disabled)
[email protected] (installed, disabled)
[email protected] (installed, disabled)
[email protected] (installed, enabled)
Database type
MongoDB

Database version
v6.0.4

Well, I figured since all other browsers that come to mind are a fork of Chrome I shouldn't test them.

I repeated the process on Edge version 123.0.2420.65 (Official build) (64-bit) and it works as I expected it to work.

To recap, Chromium-based browsers seem to work while Firefox has this issue with bmp images.

Hello, I'm reproducing this bug right here on this website.

Basically, I am unable to change my profile picture when I use Firefox but I can with Chrome.

When I upload it using Firefox I get "input file contains unsupported image format" error

When I use Chrome I get no such error and I can upload the image fine and as you can see my current profile picture is reflecting that (Edit 1: was true at the time of writing this post, I've now changed it so something else).

Keep in mind I had to compress the image down for this forum because on my forum I could have uploaded the uncompressed image with Chrome due to different settings our forum has.

On our instance of nodebb at plutonium.pw I got an obscure error message instead which did not tell me anything on Firefox.

This is the file in question: https://mega.nz/file/lJJQhZgQ#hmoxBlZ1_Fpj1POqP9VKcUht88CO5jGbayHtS61BpeM
(Compressed)

Chrome Version 123.0.6312.60 (Official Build) (64-bit) Windows 10

Firefox 104.0.1 64-bit Windows 10

Hello again, I guess it's a classic when someone asks an issue and then they figure out something later.
It was my nginx config

Hello,

Whenever I attempt to use a bulk action on all the flags displayed under the /flags webpage it triggers a 503 error like below.
What's strange is that it seems the bulk actions are applied "randomly" to some flags while others remain unprocessed. What could I do to debug this?
As anyone else reported anything similar?

I'm using the following software

NodeBB version
v3.3.6

NodeBB git hash
7fb3879

NodeJS version
v18.16.0

Installed NodeBB plugins
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, disabled)
[email protected] (installed, disabled)
[email protected] (installed, disabled)
[email protected] (installed, enabled)
[email protected] (installed, enabled)
[email protected] (installed, disabled)
[email protected] (installed, disabled)
[email protected] (installed, disabled)
[email protected] (installed, enabled)

Database type
MongoDB

Database version
v6.0.4