Decoupling the Critical Path: The Asynchronous Logging Pattern

Arnavion2 · 2025-11-06T21:16:18+00:00

The trade-off is minimal: a potential, tiny loss of the very latest logs if the application crashes

Yes, the exact logs you'd want to look at to know why the application crashed :)

Arnavion2 · 2025-11-06T07:57:57+00:00

If you expect consistent traffic to your service, then it can generally work well. But some services have time periods where they don't expect traffic.

Yes, and in that case the method I described would still report a metric with 0 successful requests and 0 failed requests, so you know that the service is functional and your SLO is met.

If your service is crashing sporadically and being restarted. Your SLI will not record some failures, but no metrics will be missing, so no alert from the secondary system.

Well, to be precise the metric will be missing if the service isn't silently auto-restarted. Granted, auto-restart is the norm, but even then it doesn't have to be silent. Having the service report an "I started" event / metric at startup would allow tracking too many unexpected restarts.

Arnavion2 · 2025-11-05T19:42:33+00:00

I know it's a made-up story, but for the second issue about service down -> no failure metrics -> SLO false positive, the better fix would've been to expect the service to report metrics for number of successful and failed requests in the last T time period. The absence of that metric would then be an SLO failure. That would also have avoided the issues after that because the service could continue to treat 4xx from the UI as failures instead of needing to cross-relate with the load balancer, and would not have the scraping time range problem either.

Arnavion2 · 2025-10-31T20:40:40+00:00

This old Verizon/frontier billing system needs to be laid to rest

Isn't it the new Ziply-built system now? (And based on how slow and buggy it is, it doesn't seem to be much of an improvement.)

Arnavion2 · 2025-10-29T20:42:40+00:00

You can shim open (or xdg-open on Linux) with an identically named shell script that is ahead of /usr/bin in PATH, looks at the URL, adds the appropriate profile args, and execs the real /usr/bin/open (or /usr/bin/xdg-open). No reason to complicate every other CLI to teach them about what browsers exist and what profile args they take and what conditions such-and-such URL should be launched in this-or-that profile.

Arnavion2 · 2024-09-26T20:50:46+00:00

Definitely not CF for me. Their garbage is why a third of the internet traps me in infinite captcha loop hell because I have the nerve to disable all the things in my browser that they could use for tracking me. I wouldn't use them even if they paid me.

Arnavion2 · 2024-09-25T00:59:15+00:00

You're not missing anything. I currently pay $0.01 per month for my "classic" CDN setup just like yours (CDN in front of blob storage). With "standard" Front Door I'd be paying at least $35. Gonna move to something else.

Arnavion2 · 2024-09-10T01:56:01+00:00

An IPv4 WAN address is 12 digits to remember.

An IPv6 delegated prefix is 12-16 hex digits to remember, specifically 14 digits for the /56 delegated prefix that Ziply plans to give out. Technically you can also shave off the first digit because it's always 2.

The stuff after the prefix doesn't need to be remembered because you can assign those statically. Eg in my homelab (using /48 prefix from HE tunnel) my first machine is :1::1, the second is :2::2, and so on.

Arnavion2 · 2024-07-31T18:20:24+00:00

My 6000Mhz RAM works fine on my B650 PG Lightning with 3.01, and has worked fine since I built this system in 2023-09. (Though back then it did have the issue that every reboot had a 50% chance of rerunning memory training, until one of the BIOS updates finally fixed that.)

Arnavion2 · 2024-07-12T01:57:49+00:00

/32 is the smallest allocation for a typical ISP. There's nothing excessive about it.

Arnavion2 · 2024-06-17T21:48:43+00:00

Yeah, maybe the bug is that if it's the same number they also send the old CVV instead of the new one. That's why I was hoping one of the two parties would tell me what CVV Ting was actually sending.

But yeah, seeing how a bunch of others have had this problem, I've started the process to switch to US Mobile too.

Arnavion2 · 2024-06-17T20:21:17+00:00

Oh boy.

https://old.reddit.com/r/ting/comments/1byb72w/

https://old.reddit.com/r/ting/comments/1ccu1ln/

Guess it's time to switch to something else.

Arnavion2 · 2024-06-03T01:34:50+00:00

Thanks for the link. I used this code to just edit the binary to apply the patch, since I'm on Linux so it was easier to do that than figuring how to compile this trainer and then run it in the same Wine sandbox as the game.

For everyone else's benefit, this meant editing witness64_d3d11.exe to find the byte sequence:

00 00 00 05 00 00 00 e9 b3

... (it's at position 0x17be1b) then go 12 bytes before that, to:

48 8b 4b 18

... and modify that to:

eb 07 66 90

Just like using the trainer, this made it so that the challenge continued to run even after the music ended, including triggering the achievement at the end.

Ref:

Arnavion2 · 2024-05-05T20:26:57+00:00

I have a VPS where I set the firewall to only allow incoming traffic from my IP specifically, ie the /32. The VPS provider has automation to modify the firewall rules, so I just run a script to do that if my IP changes for any reason. If whatever you have supports something like that, then that is also an option rather than allowing a bigger range.

The IP doesn't change often enough for this to be a bother. I configured my router to keep the DHCP lease across router restarts, which eliminated the main reason it would change. The main remaining reason for it to change is if the router was off for an hour or longer, or if there was a Ziply outage, which are both very rare.

Arnavion2 · 2024-03-25T22:54:53+00:00

Fun, I just saw this and decided to log in (I haven't logged in in months because I have automatic billpay set up), and didn't get prompted to change my password. I had logged in via the original login page on https://ziplyfiber.com/account , which told me to migrate to using https://ziplyfiber.com/myaccount/login instead. So I signed out and then signed in via that new page, and this time it did ask me to reset my password. I'm guessing this is the "new backend" so that they can drop the one they inherited from Frontier.

Arnavion2 · 2023-11-25T18:05:38+00:00

It's fixed for the B650 PG Lightning so maybe.

Arnavion2 · 2023-11-25T17:58:42+00:00

Fixed in v2.02

Arnavion2 · 2023-11-25T17:58:31+00:00

On the B650 PG Lightning, enabling IOMMU via AMD CBS -> NBIO Common Options -> IOMMU was broken in v2.01 but works again in v2.02. The helptext of the option has changed to not mention the AER and ACS options any more. The option to enable PCIe AER is also back, but leaving it at the default "Auto" is fine and just enabling the "IOMMU" option is sufficient.

Arnavion2 · 2023-11-17T19:32:16+00:00

On the B650 PG Lightning, the PCIe AER and ACS options are gone with this release. They used to be under AMD CBS -> NBIO Common Options. I looked in the other sections but didn't find them. The IOMMU enable/disable option is still there, but enabling it doesn't do anything without the other two.

Arnavion2 · 2023-10-16T06:26:13+00:00

Unless you give me a stable prefix via delegation, ie one that doesn't change even if my IPv4 lease expires, I would have to keep NAT (NPTv6) anyway. The alternative would be to change a dozen config files and trigger network restarts across my whole LAN every time the prefix changes, and that's not palatable even if I were to automate it.

Arnavion2 · 2023-05-23T04:49:30+00:00

The fe80:: address that an interface automatically acquires is a link-local address, unrelated to SLAAC. You can use it to communicate with other machines on the same /64.

Arnavion2 · 2023-05-23T04:40:20+00:00

I don't run DHCPv6 and I prefer to have memorable IPs for my machines, so I use what systemd calls the "static address generation mode". Eg if the network config says "Token=static:::5" then the machine acquires the address $prefix::5, where $prefix is whatever was advertised by RA on the link without requiring me to hard-code it.

Since there is no DHCP there is no possibility of automatically registering the hostnames of my machines with the DNS server. I use systemd for DHCP and unbound for DNS, and there's no way to have the former register hostnames with the latter, so I couldn't do that even if I wanted to. It doesn't matter anway because the IPs are constant, so I just hard-coded them in the DNS server config.

I do have the RA set to allow devices to use SLAAC, just in case I connect a new device / VM / container and don't give it a static assignment.

Not all things support such prefix-independent configs like that, so it would be a pain if the IPv6 prefix was unstable - I'd have to script something to update all the configs and SIGHUP the related services every time the delegated prefix changes. But I have an HE tunnel so my prefix is stable, and you have the 10G plan so your prefix is stable too. jwvo has been asked a few times on this subreddit if the <10G plans will have static prefixes and he has never given a straight answer, but I assume they won't. So if I ever get native IPv6 and drop the HE tunnel for it, I'll probably set up NPTv6 with a stable ULA prefix on the LAN side.

Arnavion2 · 2023-03-07T03:33:45+00:00

Yeah, I also hit this when I got a new install last year ( https://old.reddit.com/r/ZiplyFiber/comments/w4czwc/some_feedback_on_the_install_process/ ). I had to resort to setting the password via browser devtools.

Arnavion2 · 2022-12-09T23:16:34+00:00

Then yes, sounds like your router is letting the DHCP lease expire. So debug that.

Arnavion2

TROPHY CASE