ThatDeveloper12

I see this a lot in example code, where people wait on a process to exit and then collect it's return code using "catch wait result" and then usually something like "exit [lindex $result 3]" to return the process' exit code. This doesn't seem right at all.

Firstoff, it seems like wait already does a pretty good job of handling weird process termination. From [1]:

wait normally returns a list of four integers. The first integer is the pid of the process that was waited upon. The second integer is the corresponding spawn id. The third integer is -1 if an operating system error occurred, or 0 otherwise. If the third integer was 0, the fourth integer is the status returned by the spawned

I've noticed watching some twitch streams that SAPS announcements that are meant to trigger at specific points in the campaign or in response to specific events can sometimes trigger randomly in place of generic "ambiance" announcements. For example, the announcement warning about auditory hallucinations rising from below in the delta labs can sometimes trigger in the middle of abyss.

Hi, I'm relatively new to alpine and have a couple of questions:

(1) With new releases every 6 months and each release's community repo supported for that amount of time, does that mean packages in the community repo will stop seeing updates then? (making it a good idea to continually move to the latest release if you're using community packages)

(2) After upgrading to a new release, eg. via [1], what's the best way to find old packages that are a holdover from the previous release? Is there a way to list packages based on what release's main/community repos they came from?

[1] https://wiki.alpinelinux.org/wiki/Upgrading_Alpine_Linux_to_a_new_release_branch

Clearly the normal API (https://developers.stoat.chat/api-reference/) is not useful for this. It assumes you're making changes as a specific user with a specific user's permissions, among other limitations.

I'm interested in implementing something that can take an export from some other chat platform and stuff it into a local Stoat server, as if the message history had always been sent through stoat. Intact messages, attachments, message-sent timestamps, etc, etc, including mapping of accounts on the old chat platform to those on the stoat server.

There doesn't seem to be any existing API for this kind of large-scale editing of history. (on eg. discord you could partially achieve this wit

Have many legacy IPv4-only devices, and an IPv6-only upstream. Looking for an implementation of, or way to implement, NAT46+DNS46. Right now it seems Fortinet are shipping something packaged (the only ones in fact), but I'm looking for something I can set up on generic linux/FreeBSD.

CLAT/464xlat is explicitly out of scope because it requires cooperation on the PLAT side. Actual NAT46 translation is vastly preferable and would enable connections over IPv6 directly to IPv6-only hosts. To the rest of the world the network appears IPv6-capable, or at worst like a NAT66, and everyone can get on with their lives.

For those unfamiliar, NAT46/DNS46 is where DNS queries are received from IPv4 clie

I have an array that will go very long periods (days, weeks) between bursts of activity. Is there a good way to make it spin down after X number of hours idle to conserve a large amount of power consumption? Running openZFS on ubuntu/debian.

I suppose what I'm asking for might be impossible without splitting off a separate thread/process. I would kinda like to avoid that if possible, being as the interpreter is a baremetal(-ish) TCL implementation that might not support it very well.

Basically, I have a main program which does a bunch of stuff, but generally isn't event driven. It's a traditional program that does it's own thing. Parallel to this, there's a source of external events (specifically, a serial-port-ish channel) through which messages arrive. Ideally each time there's new data a handler would fire, process it, maybe send a response back through the channel in a timely manor, and maybe drop a message into a queue for

I'm currently working on some pretty heavily WIP language experiments, and something I need is the ability to store some information about a value out-of-band, for as long as that value remains unchanged. Something like:

% set myvar 10

% tag myvar banana

% puts $myvar

10

% tag --read myvar

banana

% set myvar2 $myvar

% puts $myvar2

10

% tag --read myvar2

banana

% set myvar2 20

% puts $myvar2

20

% tag --read myvar2

<empty string>

% proc myproc {myarg} {tag --read myarg}

% myproc myvar

banana

I've looked into whether I can hack something together with traces, or maybe hack set, proc, etc and replace them with smart alternatives that can update a global tag registry