umurmur: improve init script #27566

Ra2-IFV · 2025-09-30T15:21:06Z

📦 Package Details

Maintainer: @Ansuel @neheb
_{(You can find this by checking the history of the package Makefile.)}

Description:
Fixing good

🧪 Run Testing Details

I swear I tested the binary. As for the init script not yet. I'm burning out.

OpenWrt Version: 16416782f194d1850a9d9accf02f04832a7fcea4
OpenWrt Target/Subtarget: aarch64
OpenWrt Device: aarch64 generic

✅ Formalities

I have reviewed the CONTRIBUTING.md file for detailed contributing guidelines.

Ra2-IFV · 2025-09-30T15:23:56Z

Tue Sep 30 15:22:14 2025 daemon.info uMurmurd[4979]: uMurmur version 0.3.0 ('Loopy') protocol version 1.2.4
Tue Sep 30 15:22:14 2025 daemon.info uMurmurd[4979]: Visit https://github.com/umurmur/umurmur
Tue Sep 30 15:22:18 2025 daemon.warn uMurmurd[4979]: SSL: verify error:num=18:self-signed certificate:depth=0:/CN=Mumble User
Tue Sep 30 15:22:18 2025 daemon.info uMurmurd[4979]: User provided admin password - [1] REDACTED
Tue Sep 30 15:22:18 2025 daemon.info uMurmurd[4979]: User REDACTED authenticated - [1] REDACTED
Tue Sep 30 15:22:18 2025 daemon.info uMurmurd[4979]: New UDP connection from REDACTED on port 61142 - [1] REDACTED

BKPepe · 2025-09-30T15:44:06Z

Why have you created PR for updating umurmur, when already there is one?
#27562

net/umurmur/Makefile

BKPepe · 2025-09-30T15:48:50Z

net/umurmur/Makefile

+	$(INSTALL_DIR) $(1)/etc/config
+	$(INSTALL_CONF) $(CURDIR)/files/umurmur.conf $(1)/etc/config/umurmur
 	$(INSTALL_DIR) $(1)/etc/umurmur
+	$(INSTALL_CONF) $(PKG_BUILD_DIR)/umurmur.conf.example $(1)/etc/umurmur/umurmur.conf


Why we are shipping two files?

This has the same structure as the config file, which you are adding.

No, we dont really need two config files, this leads to misunderstandings, because you dont know, which one should use and copy.

One is for uci, that saves some critical things, like host, port and config location. Why hardcoding the config location? just let procd & uci do these things, plz....
Another one is for mumble.
pkgname.conf and pkgname.init is common practice, isnt it? Do you have a better idea?
I think it's okay on user side, add comments in Makefile? It's not shipped to end user.

Why comments in the Makefile? These are not necessary at all.

Okay I'll delete them.

Well, I mean the 1-4 lines on the top, okay to delete, or keeping them?

BKPepe · 2025-09-30T15:49:49Z

Love story does not belong to the commit description:

I spent 3 hours fixing the variable simply because
I didn't read fking full build log.
So poor I am. I can never be a good developer nor maintainer.  ;(

🤷

net/umurmur/Makefile

Ra2-IFV · 2025-09-30T18:44:45Z

Love story does not belong to the commit description:

I spent 3 hours fixing the variable simply because
I didn't read fking full build log.
So poor I am. I can never be a good developer nor maintainer.  ;(

🤷

Yeah, I know, just want someone to hear me crying loudly, in front of a computer but it's not running JavaScript.
Thank you for checking my commit messages! Am I doing better than before on this?

Ra2-IFV · 2025-09-30T18:56:07Z

Why have you created PR for updating umurmur, when already there is one? #27562

When I was struggling boxing with errors, I didn't know that you have an existing pr. sry.

Ra2-IFV · 2025-09-30T19:08:32Z

@BKPepe And your solution is absolutely better. I simply removed *_LIBRARIES because we have *_LIB_PATH and *_INCLUDE_PATH, it should't point to a directory, and I don't know what does this do, so just removed.
Thanks teacher, another brilliant lesson!

Ra2-IFV · 2025-09-30T20:38:11Z

Great! Both binary and init script passed test in my case. I still can't have a bundled apk file tho

OpenWrt ~ # service umurmur info
{
        "umurmur": {
                "instances": {
                        "instance1": {
                                "running": true,
                                "pid": 9594,
                                "command": [
                                        "/usr/sbin/umurmurd",
                                        "-d",
                                        "-c",
                                        "/etc/umurmur/umurmur.conf",
                                        "-a",
                                        "0.0.0.0",
                                        "-A",
                                        "::",
                                        "-b",
                                        "64738",
                                        "-B",
                                        "64738"
                                ],
                                "term_timeout": 5
                        }
                },
                "triggers": [

                ]
        }
}

Ra2-IFV · 2025-09-30T20:42:27Z

Test formalities failed because: umurmur!: ......
Because this is a breaking change, default conf location changed.
Is it possible to have a post-install script to migrate conf file?

Move these files to OpenWrt repo. For pending pull request, see link below. Link: openwrt/packages#27566 Signed-off-by: Ryan Keane <[email protected]>

wehagy · 2025-10-02T00:42:41Z

Is it possible to have a post-install script to migrate conf file?

The correct way to do this is to use UCI defaults. Search the repository for *.defaults to see some examples.

Test formalities failed because: umurmur!: ......
Because this is a breaking change, default conf location changed.

The formalities check is correct. Please read the CONTRIBUTING.md and Submission Guidelines:

Have a useful commit subject prefixed with the package name.
Don't capitalize first word after the prefix.

BKPepe · 2025-10-02T07:29:40Z

Yeah, I know, just want someone to hear me crying loudly, in front of a computer but it's not running JavaScript.

You could use PR description for it, but not commit itself as it stays in the history forever, but yeah, mistakes happens.
Sometimes, it is better to take a time, summarize what you want to say as currently this simple PR has almost 30 comments and that's not good. Hards to follow it, etc.

net/umurmur/files/umurmur.init

BKPepe

I went through your proposed changes, but unfortunately some of them don’t quite make sense and I don’t see much value in them. I’d recommend reviewing how init scripts and UCI config files are written and what they’re meant to do — the OpenWrt documentation explains it well. If you’re still uncertain, you can always ask tools like ChatGPT, Claude AI, or GitHub Copilot for help. There’s absolutely nothing wrong with using them — just remember to double-check their suggestions.

BKPepe · 2025-10-07T14:27:13Z

net/umurmur/files/umurmur.conf

+option umurmur 'config'
+	option conffile '/etc/umurmur/umurmur.conf'


Why conffile? Does it need to be conffile?

What about option config_path or config_file as it it common in other uci config files in this repository?

I'm stubborn, I think checking random words from AI is so tiring and can't learn anything
I grown up by googling, reading mans and wikis, and viewing others codes. Sometimes (Usually, actually?) I'm careless

Can you mark conversation resolved by yourself? I'm too afraid to mark it resolved by myself now, just to make sure that everything is reviewed by you

BKPepe · 2025-10-07T14:27:45Z

net/umurmur/files/umurmur.conf

+	option address4 '0.0.0.0'
+	option address6 '::'
+	option port4 '64738'
+	option port6 '64738'


Doing this just for IP protocol and port does it make sense to introduce such breaking change?

Not a breaking change I guess, by default it listens to that address and port

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME umurmurd 200752 umurmur 3u IPv4 307954 0t0 TCP *:64738 (LISTEN) umurmurd 200752 umurmur 4u IPv6 307955 0t0 TCP *:64738 (LISTEN) umurmurd 200752 umurmur 5u IPv4 307956 0t0 UDP *:64738 umurmurd 200752 umurmur 6u IPv6 307957 0t0 UDP *:64738

This needs to be reworked — the intent was misunderstood. Right now you’re adding UCI and init options to allow separate IPv4/IPv6 addresses and different ports for each IP. In practice, separate ports are rarely used and will complicate client and admin setups. On typical Linux systems a single port bound on a dual-stack address (e.g. ::) will handle both IPv6 and IPv4 (unless the system explicitly enforces IPv6-only sockets), so a single port option is the norm.

Adding separate ports options changes the configuration schema and defaults, which risks a breaking change for existing deployments. Please revert the separate-port fields and expose only a single port plus a bind_address option (default :: or 0.0.0.0), and keep the new options optional so existing UCI configs continue to work. Also ensure the init script runs the daemon in the foreground under procd (no -d/daemonize).

This package doesn't use UCI before, shouldn't breaking existing things.
Removing separate ports option makes sense, but I suggest keeping both 0.0.0.0 and :: as I explained before.
You misunderstood the -d flag, it makes it run in foreground, default behavior is fork to background.

BKPepe · 2025-10-07T14:28:12Z

net/umurmur/files/umurmur.init

+#!/bin/sh /etc/rc.common
+# Copyright (C) 2006-2008 OpenWrt.org


Where did you take this copyright and how are you affilated to it?

From upsteam? You can check here
Not sure what to do with this line if I overhauled the whole file.

Then please look at CONTRIBUTING.md at this repository or Contributing guidelines, which are available at OpenWrt wiki.

BKPepe · 2025-10-07T14:28:25Z

net/umurmur/files/umurmur.init

+        procd_set_param stdout 1
+        procd_set_param stderr 1


Do you need to really have enabled stdout and stderr?

Uh, I give -d in CLI, it does print logs

# bash -xc 'umurmurd -d &2>/dev/null ' + umurmurd -d # INFO: OpenSSL library initialized (version: OpenSSL 3.5.3 16 Sep 2025) INFO: Setting default channel 'Lobby' INFO: Adding channel 'Lobby' parent 'Root' INFO: Adding channel 'Silent' parent 'Root' INFO: Adding channel 'Chatroom' parent 'Root' INFO: No channel links found in configuration file. FATAL: bind 0.0.0.0 64738: Address in use

BKPepe · 2025-10-07T14:31:15Z

net/umurmur/files/umurmur.conf

@@ -0,0 +1,6 @@
+option umurmur 'config'


In this UCI config, I miss options like:

enabled

user:group

password for Mumble server, if someone wants to have it private

BTW: I think AI such as ChatGPT, Copilot might help you with this one instead of reinveinting a wheel here

Run user & group, password cannot be specified in CLI, but in conf file
Is this that necessary?

I basically learn everything from wiki and @1715173329 .
Some pages on wiki is outdated, I registered an account for editing but no contributions so far.

Run user & group
Is this that necessary?

It’s not absolutely necessary for functionality, but it’s strongly recommended for security reasons. Running the daemon under root means any potential vulnerability could lead to full system compromise. By specifying a dedicated user and group in the UCI config, the service can drop privileges after startup and run in a restricted context. This is standard practice for most network services in OpenWrt and Linux in general.

Uh, done. Most packages doesn't do this though

BKPepe · 2025-10-07T14:32:27Z

net/umurmur/files/umurmur.conf

+	option port4 '64738'
+	option port6 '64738'


Why do you need to specify port for IPv4 and IPv6? That seems really weird for me.
That is not even in umurmur/umurmur@209edb5

Because it's the default?

And it can listen on different ports for IPv4 & 6.
If you only specify port for one IP protocol, another doesn't follow that.

umurmurd 200844 umurmur 3u IPv4 315714 0t0 TCP *:64738 (LISTEN) umurmurd 200844 umurmur 4u IPv6 315715 0t0 TCP *:64739 (LISTEN) umurmurd 200844 umurmur 5u IPv4 315716 0t0 UDP *:64738 umurmurd 200844 umurmur 6u IPv6 315717 0t0 UDP *:64739

net/umurmur/Makefile

BKPepe · 2025-10-07T14:33:34Z

net/umurmur/Makefile

-	-DMBEDTLS_LIBRARIES="$(STAGING_DIR)/usr/lib" \
+	-DMBEDTLS_LIBRARIES="$(STAGING_DIR)/usr/lib/libmbedtls.so" \


This needs to be done in separate commit, but I am not sure what are you fixing here.

Because *_LIBRARIES should point to files, not directories

https://github.com/umurmur/umurmur/blob/209edb5c887e5a5d3ab2c95ab4a8aeb8c1e6e8f3/cmake/Modules/FindMbedTLS.cmake#L41-L42

And what build error have you experienced? I dont see that it fails on buildbots.

Won't be an error because MbedTLS_INCLUDE_DIRS is correct, but this variable is wrong indeed

What about other libraries such as mbedcrypto, mbedx509? 🤔

BKPepe · 2025-10-07T14:35:30Z

net/umurmur/files/umurmur.init

+        config_get address4 "config" "address4" '0.0.0.0'
+        config_get address6 "config" "address6" '::'


Sorry, but what are you trying to do it here?

Why don't e.g. do bind_address as ::It would listen on IPv4 and IPv6.

that makes sense

But sadly that flag needs a valid address, can't be empty
Or I have to write more if lines in script, worth or not?

Ra2-IFV · 2025-10-07T19:34:32Z

net/umurmur/files/umurmur.defaults

@@ -0,0 +1,4 @@
+if [ -f '/etc/umurmur.conf' ]; then
+  [ -f '/etc/umurmur/umurmur.conf' ] && mv /etc/umurmur/umurmur.conf{,.apk-new}


Uh, is it okay to rename to apk-new?

Ra2-IFV · 2025-10-07T19:40:27Z

@BKPepe 57 comments... I'll try not being that lazy next time....
@wehagy When do uci-default scripts run, precisely? Wiki says

Scripts in /etc/uci-defaults will get executed at every first boot (i.e. after a clean install or an upgrade)

A fresh package install and existing package upgrade?

BKPepe · 2025-10-08T06:19:16Z

I'll try not being that lazy next time....

I explored a possible alternative using AI, which might serve as a cleaner skeleton for future improvements. It’s just an idea that could make the configuration easier to work with.

Config:

config umurmur 'main'
	option enable '1'                    
	option user 'umurmur'
	option group 'umurmur'
	option port '64738'                  
	option bind_address '0.0.0.0'       
	option max_users '100'
	option welcometext 'Welcome'
	option password ''                   
	option ssl_cert '/etc/umurmur/umurmur.crt'
	option ssl_key '/etc/umurmur/umurmur.key'
	option logfile '/var/log/umurmur.log'
	option loglevel 'info'             
	option banfile '/etc/umurmur/bans.txt'
	option channels '/etc/umurmur/channels.conf'

Init:

#!/bin/sh /etc/rc.common
# Init script for uMurmur (Mumble server)
# OpenWrt style - supports UCI config

START=95
STOP=10
USE_PROCD=1
PROG=/usr/sbin/umurmurd

start_service() {
	config_load umurmur
	config_get_bool enabled main enable 0
	[ "$enabled" -eq 1 ] || {
		echo "uMurmur disabled in UCI config"
		return 1
	}

	config_get user main user 'umurmur'
	config_get group main group 'umurmur'
	config_get port main port '64738'
	config_get bind main bind_address '0.0.0.0'
	config_get max_users main max_users '100'
	config_get welcometext main welcometext 'Welcome to uMurmur!'
	config_get password main password ''
	config_get ssl_cert main ssl_cert '/etc/umurmur/umurmur.crt'
	config_get ssl_key main ssl_key '/etc/umurmur/umurmur.key'
	config_get logfile main logfile '/var/log/umurmur.log'
	config_get loglevel main loglevel 'info'
	config_get banfile main banfile '/etc/umurmur/bans.txt'
	config_get channels main channels '/etc/umurmur/channels.conf'

	
	cat <<-EOF > /var/etc/umurmur.conf
	# Auto-generated by /etc/init.d/umurmur
	port = $port
	bindaddr = $bind
	max_users = $max_users
	password = $password
	welcometext = "$welcometext"
	ssl_cert = $ssl_cert
	ssl_key = $ssl_key
	logfile = $logfile
	loglevel = $loglevel
	banfile = $banfile
	channels = $channels
	EOF

	procd_open_instance
	procd_set_param command $PROG -c /var/etc/umurmur.conf
	procd_set_param user "$user"
	procd_set_param respawn
	procd_close_instance
}

stop_service() {
	procd_kill umurmur
}

**That said, it’s worth checking whether all these options actually exist and work as expected — this needs proper testing. As I mentioned, AI can be both a good and a bad helper. There’s no need to reinvent the wheel if a solid solution already exists.

Please take a look and see if this approach really makes sense.**

Ra2-IFV · 2025-10-08T08:32:35Z

Please take a look and see if this approach really makes sense.**

I know this approach, but is it okay to violate the configuration file?
I mean, is it really okay to integrate config with uci so deeply? It makes the whole thing more complicated, and, before, uci config is only for critical things, and the left for config file. It's that simple.
This approach let users take care of 3 files, uci, ban file and channel file. And if umurmur introduces more features (more configurable things) in the future it will be even more complicated!
I see run user run group can be set via procd, I'll take that

BKPepe · 2025-10-10T07:11:12Z

I mean, is it really okay to integrate config with uci so deeply? It makes the whole thing more complicated, and, before, uci config is only for critical things, and the left for config file. It's that simple.

Well, why not? Why yes? I mean, if you’d like to have UCI config, then you’d probably want LUCI integration as well, right? 😇

Here is the screenshot how it could look from AI:

Ra2-IFV · 2025-10-10T09:39:16Z

I'm not planning to add luci support, because I don't touch luci related things...
I still suggest keeping it simple, at least, not in this commit, let's make it work first, plz

BKPepe · 2025-10-10T09:42:42Z

If you’re not planning to add LuCI integration, I don’t really see the point of introducing a UCI config at all. UCI makes sense when you want to expose settings through LuCI or allow runtime reconfiguration — but if the goal is only to store the port and IP address, that’s quite limited. In that case, it feels like unnecessary complexity and a potential breaking change without a clear benefit. Dne pá 10. 10. 2025 11:39 uživatel IFV ***@***.***> napsal:

…

*Ra2-IFV* left a comment (openwrt/packages#27566) <#27566 (comment)> I'm not planning to add luci support, because I don't touch luci related things... I still suggest keeping it simple, at least, not in this commit, let's make it work first, plz — Reply to this email directly, view it on GitHub <#27566 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7IDVDWIZWYVT3FGVZKACT3W55FVAVCNFSM6AAAAACH5E2EFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOBZGA4TMOJWHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Ra2-IFV · 2025-10-10T11:11:00Z

Well, maybe, I have to learn them from scratch and may take a long time, and if so this will be my first try
for now just some minor improvements

Fix CMake MBEDTLS_LIBRARIES variable. It should set to a list of files, instead of directories. Signed-off-by: Ryan Keane <[email protected]>

Ra2-IFV · 2025-10-12T09:22:19Z

No more amending required on this PR, I guess, LuCI support is on the way, uci config support is the base :)

BKPepe

I don’t think this is ready to be merged at this point. And honestly, asking for it to be merged just to have your first contribution checked off your to-do list isn’t the right approach — that’s not how it works, unfortunately.

You mentioned that you plan to create a simple UCI configuration file and mark it as a conffile. That’s fine in principle — it ensures the file won’t be overwritten when new updates are installed. Instead, users or administrators who install the package would be responsible for reviewing and applying any config changes themselves (e.g. through the -opkg or -apk suffix).

That said, maybe I’m being a bit strict here, but we simply can’t add a UCI config that offers only two options and isn’t fully thought through. This is a small change, but one that could introduce breaking changes just for the sake of having something merged — especially if you don’t actively use umurmur yourself.

umurmur is actually a great package to learn from: it’s simple enough, but it still needs to be properly implemented and covered from all angles.

Right now, it would be better to make this more solid — for example, by preparing a LuCI integration later on.
But first, you should start with an init script, then gradually add the UCI config and adjust the init script accordingly. Or, if needed, spend more time on self-study and prepare it properly so that it’s truly ready for merging.

Ra2-IFV · 2025-10-21T21:11:56Z

Roger, sir. But I want to finish this PR asap so I'll stage uci config related changes in another branch for uses ( luci )

Breaking change: Config file location now defaults to: /etc/umurmur/umurmur.conf And with uci-defaults script to migrate. Init script is now in "files" directory, instead of from upstrem. uMurmur example config file is now from upstream example file. Init script now calls procd to monitor service state. Signed-off-by: Ryan Keane <[email protected]>

BKPepe · 2025-10-30T08:54:37Z

net/umurmur/files/umurmur.init

+STOP=01
+USE_PROCD=1
+
+CONF="umurmurd"


This is used where?

BKPepe · 2025-10-30T08:54:49Z

net/umurmur/files/umurmur.init

+
+start_service() {
+        local user group
+        user=umurmur group=umurmur


Why this is not defined in the config file?

BKPepe · 2025-10-30T08:57:03Z

I need to close this as this is not ready to be merged. Because you removed init file and config file from umurmur (umurmur/umurmur@209edb5), we can not fix the init script in the released version (there is a bug with moved binary) and we need to ship our own init script file, which I will do.

Ra2-IFV changed the title ~~umurmur: Bump to 0.3.1~~ umurmur: Bump to 0.3.1, improve init script Sep 30, 2025

BKPepe requested changes Sep 30, 2025

View reviewed changes

BKPepe reviewed Sep 30, 2025

View reviewed changes

net/umurmur/Makefile Outdated Show resolved Hide resolved

Ra2-IFV force-pushed the feat_umurmur_bump branch 2 times, most recently from 1a9ab0e to b7f51e2 Compare September 30, 2025 20:36

Ra2-IFV mentioned this pull request Sep 30, 2025

Feat: Remove OpenWrt related files to simplify umurmur/umurmur#223

Merged

wehagy changed the title ~~umurmur: Bump to 0.3.1, improve init script~~ umurmur: improve init script Oct 2, 2025

wehagy added the enhancement label Oct 2, 2025

Gisi0 reviewed Oct 6, 2025

View reviewed changes

net/umurmur/files/umurmur.init Outdated Show resolved Hide resolved

Ra2-IFV force-pushed the feat_umurmur_bump branch from b7f51e2 to cff830d Compare October 7, 2025 11:44

Ra2-IFV requested a review from BKPepe October 7, 2025 14:02

BKPepe requested changes Oct 7, 2025

View reviewed changes

Ra2-IFV commented Oct 7, 2025

View reviewed changes

Ra2-IFV force-pushed the feat_umurmur_bump branch from cff830d to 8dc72c7 Compare October 10, 2025 09:41

Ra2-IFV force-pushed the feat_umurmur_bump branch from 8dc72c7 to 0b07de2 Compare October 10, 2025 09:44

umurmur: correct CMake variable

5f200e1

Fix CMake MBEDTLS_LIBRARIES variable. It should set to a list of files, instead of directories. Signed-off-by: Ryan Keane <[email protected]>

BKPepe added the needs work label Oct 20, 2025

BKPepe requested changes Oct 20, 2025

View reviewed changes

Ra2-IFV force-pushed the feat_umurmur_bump branch from 0b07de2 to 24342a6 Compare October 21, 2025 21:40

BKPepe requested changes Oct 30, 2025

View reviewed changes

BKPepe closed this Oct 30, 2025

		option umurmur 'config'
		option conffile '/etc/umurmur/umurmur.conf'

		#!/bin/sh /etc/rc.common
		# Copyright (C) 2006-2008 OpenWrt.org

		-DMBEDTLS_LIBRARIES="$(STAGING_DIR)/usr/lib" \
		-DMBEDTLS_LIBRARIES="$(STAGING_DIR)/usr/lib/libmbedtls.so" \

		config_get address4 "config" "address4" '0.0.0.0'
		config_get address6 "config" "address6" '::'

		@@ -0,0 +1,4 @@
		if [ -f '/etc/umurmur.conf' ]; then
		[ -f '/etc/umurmur/umurmur.conf' ] && mv /etc/umurmur/umurmur.conf{,.apk-new}

umurmur: improve init script #27566

umurmur: improve init script #27566

Uh oh!

Conversation

Ra2-IFV commented Sep 30, 2025

📦 Package Details

🧪 Run Testing Details

✅ Formalities

Uh oh!

Ra2-IFV commented Sep 30, 2025

Uh oh!

BKPepe commented Sep 30, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

This comment was marked as outdated.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

BKPepe commented Sep 30, 2025

Uh oh!

Uh oh!

Ra2-IFV commented Sep 30, 2025

Uh oh!

Ra2-IFV commented Sep 30, 2025

Uh oh!

Ra2-IFV commented Sep 30, 2025

Uh oh!

Ra2-IFV commented Sep 30, 2025

Uh oh!

Ra2-IFV commented Sep 30, 2025

Uh oh!

wehagy commented Oct 2, 2025

Uh oh!

BKPepe commented Oct 2, 2025

Uh oh!

Uh oh!

BKPepe left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Ra2-IFV Oct 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Ra2-IFV Oct 7, 2025 •

edited

Loading