CPU emulator leads to strange memory issues #3312

dtinth · 2023-06-14T11:28:49Z

The solution

edited

Download the build of Bun with “baseline” in the name

https://github.com/oven-sh/bun/releases/latest/download/bun-linux-x64-baseline.zip

if using Proxmor, follow this screenshot

Original issue:

What version of Bun is running?

0.6.9

What platform is your computer?

Linux 5.4.0-45-generic x86_64 x86_64

What steps can reproduce the bug?

repro.js

Bun.serve()

(It is a minimal reproduction)

What is the expected behavior?

Bun starts a server (which does nothing).

What do you see instead?

1 | Bun.serve();
   ^
TypeError: 湕捩摯潨瑳慮敭⁳畭瑳愠牬慥祤戠湥潣敤潦⁲潮⹷渊睥唠䱒椨灮瑵⸩潨瑳慮敭猠潨汵潤琠敨琠楲正.硅数瑣摥䀠浩潰瑲琠瑳牡⁴楷桴愠猠牴湩牯甠汲⤨䠀呔⁐破⁸桷汩敲潳癬湩慰正条笧絳‧瑡✠獻
 code: "ERR_INVALID_ARG_TYPE"

      at �����������������������������������������:1:0

Additional information

The repro above is just for testing. I ran into this error while trying to run an actual app inside a Docker container.

I went ahead and downloaded https://github.com/oven-sh/bun/releases/download/bun-v0.6.9/bun-linux-x64.zip and run it outside the Docker container and get the same error and reduced the code to the above repro script. The host OS is Ubuntu 20.04.

The text was updated successfully, but these errors were encountered:

trnxdev · 2023-06-14T15:14:01Z

Can you change the name to something like "TypeError: Random symbols when calling Bun.serve()", it looks very weird and takes up too much space.

trnxdev · 2023-06-14T15:15:07Z

It might have something to do with your linux version, the recommended is 5.6+ (screenshot from readme)

Jarred-Sumner · 2023-06-14T15:16:31Z

The bug is a memory issue. The text is stack memory

Doesn't reproduce on macOS, but will try on Linux

trnxdev · 2023-06-14T15:17:39Z

The bug is a memory issue. The text is stack memory

Doesn't reproduce on macOS, but will try on Linux

I tried it on a recent version of linux, it just doesn't do anything. no output (just keeps it alive)
my linux version: Linux tiramifybox 6.3.6-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC x86_64 GNU/Linux

cirospaciari · 2023-06-14T15:44:25Z

The bug is a memory issue. The text is stack memory

Doesn't reproduce on macOS, but will try on Linux

on Debian 10 Kernel 4.19.0-24-amd64 and on Debian 12 Kernel 6.1.0-9-amd64, got no error, just keep the process alive because the server is alive on port 3000. Will try with Ubuntu 20.04

trnxdev · 2023-06-16T09:39:16Z

Will try with Ubuntu 20.04

Any progress on it? @cirospaciari

cirospaciari · 2023-06-16T09:54:22Z

We a

Will try with Ubuntu 20.04

Any progress on it? @cirospaciari

We added better validation on Bun.serve this probably solves the issue, can you check on the latest canary to see if it is solved?

trnxdev · 2023-06-16T10:17:19Z

@dtinth

dtinth · 2023-06-16T10:32:58Z

Still error, but error message is now shorter:

$ wget https://github.com/oven-sh/bun/releases/download/canary/bun-linux-x64.zip

$ unzip bun-linux-x64.zip

$ ./bun-linux-x64/bun bug.js

1 | Bun.serve();
   ^
TypeError: 畂⹮敳癲硥数瑣⁳湡漠橢捥t慔扲污䙬楡敬呤䕯瑸慲瑣椀慭
 code: "ERR_INVALID_ARG_TYPE"

      at �����������������������������������������:1:0

$ ./bun-linux-x64/bun bug.js 2>&1 | xxd
00000000: 3120 7c20 4275 6e2e 7365 7276 6528 293b  1 | Bun.serve();
00000010: 0a20 2020 5e0a 5479 7065 4572 726f 723a  .   ^.TypeError:
00000020: 20e7 9582 e2b9 aee6 95b3 e799 b2e2 81a5   ...............
00000030: e7a1 a5e6 95b0 e791 a3e2 81b3 e6b9 a1e6  ................
00000040: bca0 e6a9 a2e6 8da5 74e6 8594 e689 b2e6  ........t.......
00000050: b1a1 e499 ace6 a5a1 e695 ace5 91a4 e495  ................
00000060: afe7 91b8 e685 b2e7 91a3 e6a4 80e6 85ad  ................
00000070: 0a20 636f 6465 3a20 2245 5252 5f49 4e56  . code: "ERR_INV
00000080: 414c 4944 5f41 5247 5f54 5950 4522 0a0a  ALID_ARG_TYPE"..
00000090: 2020 2020 2020 6174 2000 0000 0000 0000        at .......
000000a0: 00aa aaaa aaaa aaaa aaaa aaaa aaaa aaaa  ................
000000b0: aaaa aaaa aaaa aaaa aaaa aaaa aaaa aaaa  ................
000000c0: aaaa aaaa aaaa aaaa aaaa 3a31 3a30 0a    ..........:1:0.

trnxdev · 2023-07-28T18:13:46Z

@cirospaciari we hit another case, any further progress with this?
(^ see below)

Northernside · 2023-07-28T18:13:50Z

Also happening on my end (since bun 0.7.0)

Linux 5.10.0-23-amd64 x86_64 unknown
bun 0.7.1 (e110ccf)
(With OP's attached reproduction)

bun kartoffel.js 2>&1 | xxd:
https://paste.laby.net/gapavecusi.makefile

Northernside · 2023-07-28T18:36:07Z

I upgraded my Linux kernel to 6.4.0, hoping this would fix it, but unfortunately it doesn't (maybe this info helps? idk).

cirospaciari · 2023-07-28T18:54:24Z

Still not able to reproduce, @Northernside can you share more info about your system like processor name etc?

Some systems I tried:

OS: macOS 13.3 22E252 arm64
Kernel: 22.4.0

OS: Debian GNU/Linux trixie/sid x86_64
Kernel: 6.3.0-1-amd64

OS: Ubuntu 22.04.2 LTS x86_64
Kernel: 5.19.0-43-generic

and the same on Debian 10

basically, this is the expected behavior for Bun.serve() if you do not pass any object as an option. But not able to see the same broken text, looks like a memory issue.

Northernside · 2023-07-28T20:08:44Z

It didn't occur on my macOS (Sonoma, latest beta) but it does on my VPS hosted by Dashserv (German hoster).

My VPS runs under Qemu (at least that's what I believe?) so all hardware outputs tell some weird ass things, but anyway:
https://paste.laby.net/marupohehi.m (sudo lshw)
https://paste.laby.net/bukelaboti.cs (sudo lshw -short)
https://paste.laby.net/bisewahefo.sql (sudo lscpu)

According to my hoster, the CPU is an AMD Epyc 7443 4Ghz

Northernside · 2023-07-28T20:52:26Z

Also, I can give you full SSH access to my system on which it's bugging out lol - maybe this can help you debug stuff quicker?

Jarred-Sumner · 2023-07-29T05:50:57Z

The original bug was caused by incorrect arguments type checking in Bun.serve() and has since been fixed (as of Bun v0.6.11 or so).

The error @Northernside is seeing appears to be due to using bun-linux-x64 when the machine should be using bun-linux-x64-baseline. Bun's install script is meant to auto-detect this, but if installed through Docker or on a machine which does support avx2, it will install the wrong choice. @Northernside please use the .tar.gz from https://github.com/oven-sh/bun/releases/download/bun-${version}/bun-linux-x64-baseline.zip instead of https://github.com/oven-sh/bun/releases/download/bun-${version}/bun-linux-x64.zip. In the future, we will make this work better to not need this step.

Northernside · 2023-07-29T13:13:16Z

Sorry to bother you again, I don't know if I did something wrong, or not, but even when switching to -baseline, this issue still exists 👀

I made it so that it'll always grab the baseline archive in the installer (that's why I did the grep output, don't get confused).

Did I forget/do something wrong?

Northernside · 2023-08-04T11:39:02Z

Any updates on this?
I wanted to note again that this only occurs since 0.7.0 (it all works perfectly fine in 0.6.9!) and it prevents me from being able to update & use newer versions and features.
No pressure of course, don't worry!

Jarred-Sumner · 2023-08-04T11:41:01Z

Any updates on this?
I wanted to note again that this only occurs since 0.7.0 (it all works perfectly fine in 0.6.9!) and it prevents me from being able to update & use newer versions and features.
No pressure of course, don't worry!

Does this happen for any call to Bun.serve() or specifically ones with invalid arguments (eg Bun.serve() or Bun.serve(Symbol())`)

It’s very confusing why this could still be happening and why it doesn’t seem to reproduce on any hardware I’ve tried.

Northernside · 2023-08-04T11:54:26Z

Does this happen for any call to Bun.serve() or specifically ones with invalid arguments (eg Bun.serve() or Bun.serve(Symbol())`)

Seems like it does happen on every Bun.serve() call:

It’s very confusing why this could still be happening and why it doesn’t seem to reproduce on any hardware I’ve tried.

I'm still up for giving you SSH access to my VPS with the affected hardware so that you can test/debug things etc.
What could have changed from 0.6.9 -> 0.7.0 that caused this?

Northernside · 2023-08-08T18:55:26Z

I know, I know, this might annoy you, but are you up to testing/debugging it with my hardware? I want to be able to use the newer versions of bun because they also fix a lot of issues which I'm currently experiencing on 0.6.9 (e.g. a LOT of segfaults and compatibility issues).

Northernside · 2023-08-09T00:45:27Z

Oh btw I have to correct myself, it's not from 0.6.9 -> 0.7.0 but from 0.6.9 -> 0.6.10 when this issue started occurring.

Jarred-Sumner · 2023-08-09T00:46:34Z

@Northernside if you explicitly set hostname in Bun.serve does that work, by chance? I have a hunch what the cause is

Northernside · 2023-08-09T00:48:33Z

It doesn't, unfortunately.

pak-unyil · 2023-08-16T00:00:25Z

I fix this issue by changing VPS provider

Danijel-Enoch · 2023-11-26T12:54:07Z

What is the solution pls?

still getting this:
TypeError: 湕捩摯⁥潨瑳慮敭⁳畭瑳愠牬慥祤戠⁥湥潣敤⁤潦⁲潮⹷渊睥唠䱒椨灮瑵⸩潨瑳慮敭猠潨汵⁤潤琠敨琠楲正.慢敳剕⁉慣❮⁴慨敶愠甠敳湲浡⁥牯瀠獡睳

My docker file

ahoys · 2023-12-01T22:21:06Z

Your CPU doesn't support AVX2. The first step is to make sure your CPU is recent enough for Bun.

In my case my development environment was running in a virtual machine that used CPU emulation that did not support AVX2. The solution for me was to bypass the emulation altogether and allow the VM to directly use Host CPU.

ncordin · 2024-01-01T20:34:51Z

Hello, sorry it's still not clear to me, and i'm still stuck with this ERR_INVALID_ARG_TYPE error :/

From my understading, Bun is compatible with non AVX2 machines, thanks to the baseline version. The install script is detecting AVX2 support, and fetch the correct version. Am I right?

But in my situation, it does not seems to works. I would like to run Bun on production on a VPS with Ubuntu 2204. The cat /proc/cpuinfo show my virtual CPU does not have AVX2. I think the install script correctly downloaded the baseline version.

Does that means i not to find another hoster?
Thanks for your help :)

EDIT:
It's working now :) I contacted my hosting provider, they migrate my VPS to a newer cluster. If it can help, here is the new cpuinfo:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 45
model name	: Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz
stepping	: 7
microcode	: 0x1
cpu MHz		: 2299.998
cache size	: 16384 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx hypervisor lahf_lm pti tsc_adjust xsaveopt arat

Previously the CPU name something like "KVM Common CPU"

Zantier · 2024-01-17T14:43:14Z

I'm getting the same Issue on an Ubuntu VPS, where I can't change the VM settings. I'm getting the same issue whether I use the bun installer, or download the baseline version.

I'm using Bun v1.0.23, released on 2024-01-16

/z$ bun main.ts
1 | Bun.serve();
    ^
TypeError: 畂⹮敳癲⁥硥数瑣⁳湡漠橢捥t硅数瑣摥眠扥潳正瑥琠⁯敢愠
 code: "ERR_INVALID_ARG_TYPE"

      at /z/main.ts:1:1

/z$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.1 LTS
Release:        22.04
Codename:       jammy
/z$ uname -a
Linux [redacted] 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
/z$ grep avx2 /proc/cpuinfo
/z$ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 107
model name      : QEMU Virtual CPU version 2.5+
stepping        : 1
microcode       : 0x1
cpu MHz         : 3599.936
cache size      : 16384 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm constant_tsc nopl xtopology cpuid tsc_known_freq pni cx16 x2apic hypervisor lahf_lm cpuid_fault pti
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips        : 7199.87
clflush size    : 64
cache_alignment : 128
address sizes   : 40 bits physical, 48 bits virtual
power management:

/z$

codehz · 2024-01-24T13:15:56Z

The bug is a memory issue. The text is stack memory

Doesn't reproduce on macOS, but will try on Linux

@Jarred-Sumner

湕捩摯潨瑳慮敭⁳畭瑳愠牬慥祤戠湥潣敤潦⁲潮⹷渊睥唠䱒椨灮瑵⸩潨瑳慮敭猠潨汵潤琠敨琠楲正.硅数瑣摥䀠浩潰瑲琠瑳牡⁴楷桴愠猠牴湩牯甠汲⤨䠀呔⁐破⁸桷汩敲潳癬湩慰正条笧絳‧瑡✠獻

I think it may not be a memory issue, it can be decoded into (unicode to iso-8859-1)

ÿþUnicode hostnames must already be encoded for now.
new URL(input).hostname should do the trick.

it exists in

bun/src/bun.js/api/server.zig

Line 1003 in 3447bc2

    
           JSC.throwInvalidArguments("Unicode hostnames must already be encoded for now.\nnew URL(input).hostname should do the trick.", .{}, global, exception);

and

畂⹮敳癲⁥硥数瑣⁳湡漠橢捥t硅数瑣摥眠扥潳正瑥琠⁯敢愠

can be decoded into

ÿþBun.serve expects an object

while
ÿþ = 0x255 0x254

Zantier · 2024-01-24T17:51:04Z

@codehz Thanks! I changed my code to:

Bun.serve({
  fetch(req, server) { },
});

And the error can be decoded with this python:

message = '湕捩摯⁥潨瑳慮敭⁳畭瑳愠牬慥祤戠⁥湥潣敤⁤潦⁲潮⹷渊睥唠䱒椨灮瑵⸩潨瑳慮敭猠潨汵⁤潤琠敨琠楲正.慢敳剕⁉慣❮⁴慨敶愠甠敳湲浡⁥牯瀠獡睳牯d'
message.encode('utf-16').decode('iso-8859-1')

"ÿþUnicode hostnames must already be encoded for now.\nnew URL(input).hostname should do the trick.\x00baseURI can't have a username or password\x00"

Edit: Error still happening in bun 1.0.25

hayzamjs · 2024-02-05T08:27:52Z

const fastify = require('fastify')({
    logger: false
})

const path = require('path')

fastify.register(require('@fastify/static'), {
    root: path.join(__dirname, 'public'),
})

fastify.listen({ port: 3000 }, (err, address) => {
    if (err) throw err
})

Throws very similar errors for me too, on a VM running inside Proxmox:

└──╼ #bun index.js 
229 |       return listenOptions.cb(new FST_ERR_REOPENED_SERVER(), null)
230 |     }
231 | 
232 |     server.once('error', wrap)
233 |     if (!this[kState].closing) {
234 |       server.listen(listenOptions, wrap)
            ^
TypeError: 湕捩摯潨瑳慮敭畭瑳愠牬慥祤戠湥潣敤⁤潦潮渊睥唠䱒椨灮瑵⸩潨瑳慮敭猠潨汵⁤潤琠敨琠楲正.慢敳剕⁉慣❮⁴慨敶愠甠敳湲浡牯瀠獡睳牯d
 code: "ERR_INVALID_ARG_TYPE"

      at node:http:424:69
      at /opt/Projects/Alchemilla/Landing/node_modules/fastify/lib/server.js:234:7
      at manageErr (/opt/Projects/Alchemilla/Landing/node_modules/fastify/fastify.js:595:11)
      at exit (/opt/Projects/Alchemilla/Landing/node_modules/fastify/lib/hooks.js:110:5)
      at next (/opt/Projects/Alchemilla/Landing/node_modules/fastify/lib/hooks.js:121:9)
      at hookRunnerApplication (/opt/Projects/Alchemilla/Landing/node_modules/fastify/lib/hooks.js:95:3)
      at /opt/Projects/Alchemilla/Landing/node_modules/fastify/fastify.js:577:11
      at _encapsulateThreeParam (/opt/Projects/Alchemilla/Landing/node_modules/avvio/boot.js:562:7)
      at timeoutCall (/opt/Projects/Alchemilla/Landing/node_modules/avvio/boot.js:458:5)
      at callWithCbOrNextTick (/opt/Projects/Alchemilla/Landing/node_modules/avvio/boot.js:440:7)
      at release (/opt/Projects/Alchemilla/Landing/node_modules/fastq/queue.js:149:9)
      at resume (/opt/Projects/Alchemilla/Landing/node_modules/fastq/queue.js:82:7)
      at /opt/Projects/Alchemilla/Landing/node_modules/avvio/boot.js:174:5
      at /opt/Projects/Alchemilla/Landing/node_modules/avvio/plugin.js:275:7
      at done (/opt/Projects/Alchemilla/Landing/node_modules/avvio/plugin.js:200:5)
      at check (/opt/Projects/Alchemilla/Landing/node_modules/avvio/plugin.js:224:9)

Bun version: 1.0.26

jameshibbard · 2024-02-26T10:15:26Z

I was running into exactly this issue on VBox and Bun v1.0.29.
What worked for me was downloading and running Bun as an npm package.
https://www.npmjs.com/package/@oven/bun-linux-x64-baseline

dtinth · 2024-02-26T15:16:40Z

@Jarred-Sumner Seems like people still have this issue, should this be reopened?

AriesAlex · 2024-04-06T07:33:23Z

can confirm still happening on bun 1.1.2 :(

kang49 · 2024-04-11T10:29:51Z

Confirm this issue still on Bun v.1.1.3

Ubantu version: `Ubuntu 22.04.3 LTS (GNU/Linux 5.15.0-89-generic x86_64)`

nabildroid · 2024-04-29T10:44:14Z

same issue here!

VigilioYonatan · 2024-05-12T00:08:50Z

any solution in local found docker image. but in vps TypeError: 湕捩摯⁥潨瑳?

ChiChuRita · 2024-05-17T17:16:48Z

I have the same issues in Bun v1.1.8 on a VPS with baseline version

dtinth · 2024-05-17T17:25:11Z

Seems like people still have this issue, even with the baseline version, should this be reopened?

kcoderhtml · 2024-05-25T00:54:51Z

One way to solve this issue that I found for Proxmox is to set the VM CPU type to "Host" which fixes the issue for that VM.

Thanks to @ahoys for noticing this! #3312 (comment)

nabildroid · 2024-05-25T08:12:15Z

how to set it?, like not everyone has the option to modify the type!

kcoderhtml · 2024-05-25T14:51:58Z

You have to be able to modify the vm settings, but once you can, you go to the hardware tab and then change the CPU type.

yus-ham · 2024-05-26T13:51:03Z

For people who not able to set CPU type, you can try this Bun.serve() shim

https://gist.github.com/yus-ham/36f75733f26f832efe071664cf638054

Akumzy · 2024-05-26T16:10:36Z

For people who not able to set CPU type, you can try this Bun.serve() shim

https://gist.github.com/yus-ham/36f75733f26f832efe071664cf638054

 Starting...
yanm[Bun.serve] socket client open ...
yanm[Bun.serve] socket client open ...
============================================================
Bun v1.1.10 (5102a944) Linux x64 (baseline)
Args: "/home/nebor/bun-linux-x64-baseline/bun" "--bun" "server.js"
Features: jsc dotenv transpiler_cache(4)
Builtins: "bun:jsc" "bun:main" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:os" "node:path" "node:querystring" "node:stream" "node:string_decoder" "node:tty" "node:url" "node:util" "node:util/types" "node:zlib" "node:v8"
Elapsed: 38627ms | User: 39739ms | Sys: 26830ms
RSS: 16.63GB | Peak: 10.36GB | Commit: 16.63GB | Faults: 493

panic: Segmentation fault at address 0x585B6000000
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

To send a redacted crash report to Bun's team,
please file a GitHub issue using the link below:


Illegal instruction (core dumped)

dtinth added the bug Something isn't working label Jun 14, 2023

Northernside mentioned this issue Jul 28, 2023

Importing "mysql2(/promise)" segfaults #3864

Closed

Jarred-Sumner closed this as completed Jul 29, 2023

Jarred-Sumner reopened this Jul 29, 2023

ecksun mentioned this issue Nov 23, 2023

bun build --compile throws FileNotFound on start #6251

Open

Jarred-Sumner mentioned this issue Dec 5, 2023

Tests hangs and CPU goes to 99%+ when using bun test #6751

Open

Bloodiko mentioned this issue Dec 14, 2023

Executable built with bun build --compile does not work on QEMU Virtual CPU #7268

Closed

This was referenced Mar 29, 2024

Segmentation fault on Buffer.toString #5819

Closed

index out of bounds installing dependencies on windows #9808

Closed

Jarred-Sumner mentioned this issue Apr 30, 2024

strange error for simple bun.serve() : code: ERR_INVALID_ARG_TYPE #10680

Open

yus-ham mentioned this issue May 26, 2024

code: "ERR_INVALID_ARG_TYPE" running Bun on Namecheap Webuzo ubuntu #11372

Closed

Electroid reopened this May 27, 2024

Jarred-Sumner mentioned this issue Jun 6, 2024

Bun Segfault on old x86_64 CPUs #11626

Closed

Jarred-Sumner mentioned this issue Jun 13, 2024

Sentinel Mismatch #11854

Closed

CPU emulator leads to strange memory issues #3312

CPU emulator leads to strange memory issues #3312

Comments

dtinth commented Jun 14, 2023 • edited by Jarred-Sumner

The solution

What version of Bun is running?

What platform is your computer?

What steps can reproduce the bug?

What is the expected behavior?

What do you see instead?

Additional information

trnxdev commented Jun 14, 2023

trnxdev commented Jun 14, 2023 • edited

Jarred-Sumner commented Jun 14, 2023

trnxdev commented Jun 14, 2023 • edited

cirospaciari commented Jun 14, 2023 • edited

trnxdev commented Jun 16, 2023

cirospaciari commented Jun 16, 2023

trnxdev commented Jun 16, 2023

dtinth commented Jun 16, 2023

trnxdev commented Jul 28, 2023 • edited

Northernside commented Jul 28, 2023 • edited

Northernside commented Jul 28, 2023

cirospaciari commented Jul 28, 2023 • edited

Northernside commented Jul 28, 2023 • edited

Northernside commented Jul 28, 2023

Jarred-Sumner commented Jul 29, 2023

Northernside commented Jul 29, 2023

Northernside commented Aug 4, 2023

Jarred-Sumner commented Aug 4, 2023

Northernside commented Aug 4, 2023

Northernside commented Aug 8, 2023

Northernside commented Aug 9, 2023

Jarred-Sumner commented Aug 9, 2023

Northernside commented Aug 9, 2023

pak-unyil commented Aug 16, 2023

Danijel-Enoch commented Nov 26, 2023

ahoys commented Dec 1, 2023

ncordin commented Jan 1, 2024 • edited

Zantier commented Jan 17, 2024 • edited

codehz commented Jan 24, 2024

Zantier commented Jan 24, 2024 • edited

hayzamjs commented Feb 5, 2024 • edited

jameshibbard commented Feb 26, 2024

dtinth commented Feb 26, 2024

AriesAlex commented Apr 6, 2024

kang49 commented Apr 11, 2024 • edited

Ubantu version: Ubuntu 22.04.3 LTS (GNU/Linux 5.15.0-89-generic x86_64)

nabildroid commented Apr 29, 2024

VigilioYonatan commented May 12, 2024

ChiChuRita commented May 17, 2024 • edited

dtinth commented May 17, 2024

kcoderhtml commented May 25, 2024

nabildroid commented May 25, 2024

kcoderhtml commented May 25, 2024

yus-ham commented May 26, 2024

Akumzy commented May 26, 2024

dtinth commented Jun 14, 2023 •

edited by Jarred-Sumner

trnxdev commented Jun 14, 2023 •

edited

trnxdev commented Jun 14, 2023 •

edited

cirospaciari commented Jun 14, 2023 •

edited

trnxdev commented Jul 28, 2023 •

edited

Northernside commented Jul 28, 2023 •

edited

cirospaciari commented Jul 28, 2023 •

edited

Northernside commented Jul 28, 2023 •

edited

ncordin commented Jan 1, 2024 •

edited

Zantier commented Jan 17, 2024 •

edited

Zantier commented Jan 24, 2024 •

edited

hayzamjs commented Feb 5, 2024 •

edited

kang49 commented Apr 11, 2024 •

edited

Ubantu version: `Ubuntu 22.04.3 LTS (GNU/Linux 5.15.0-89-generic x86_64)`

ChiChuRita commented May 17, 2024 •

edited