Essem
> Hey, got any news ? Should I close the issue ? I feel like it could be due to a change in Discord's embed format for tenor gifs, not...
> It likely is an issue with the embed format as I am getting several commands failing with the error > > Message: Request ended prematurely due to a closed...
This *should* be fixed by now, especially on the main bot where message content is no longer available. If this is still an issue on self-hosted instances, please comment and...
Figured out that passing in raw file buffers (as done with 61758fa3bb57faa92633dfc34ab5e0925ef73e7a) seems to lower memory usage a bit. I assume that it tries to cache the images in memory...
> [error (1).txt](https://github.com/esmBot/esmBot/files/7629087/error.1.txt) This is probably a memory leak too. Gif used is [this.](https://tenor.com/view/smurfs-dance-party-smurf-dance-smurf-gif-22270951) This is unrelated, it's probably due to some cache cleanup stuff.
New findings: this seems to happen regardless of whether or not Magick++ is used, which leads me to believe that it's an issue with how node-addon-api and NAPI handle buffers...
The speed parameter is stored as an `int` on the native side, so any decimal values are rounded to the largest integer less than that value.
Seems to no longer occur, closing.
Never mind, I might take a closer look at this now that I know the cause.
Seems related to the 3-second slash command response timeout. df43f9eb9d9f1b9db756efa9dbbba67779a4bf33 makes a first attempt to resolve this.