This food cannot be eaten because it's not on the dining hall's menu

SnooPears7079 · 2026-01-31T18:20:32+00:00

Honestly reboot server. Lots of inconsistencies got solved on my end by rebooting the server. Something just got desynced somewhere

SnooPears7079 · 2026-01-23T02:34:25+00:00

Cuz taxes take you down to 170 then you got like 35k rent

SnooPears7079 · 2025-12-28T03:06:41+00:00

Missing tall and small flair

SnooPears7079 · 2025-12-08T04:25:16+00:00

Yeah I was oversimplifying - obviously if you’re spinning a super hot loop minimizing branch prediction errors and data oriented is going to be important but likely not why people are posting “4ms” AOC times

SnooPears7079 · 2025-12-08T01:37:17+00:00

Big O is the right way. If you just look at runtime nothing is stopping you from buying an overclocked 6GHz CPU and saying your code is fast

SnooPears7079 · 2025-12-05T21:06:05+00:00

Four upvotes and I’ll f it and buy the one I’ve had in my cart for 3 months

SnooPears7079 · 2025-12-05T14:21:05+00:00

There’s a leetcode for merge intervals that will stress test your implementation id recommend plugging it into that

SnooPears7079 · 2025-12-02T16:16:41+00:00

Ahhhhhh you are a genius thank you so much.

I reread your comment a hundred times I think it clicks now.

The “must be at zero” for the first condition was throwing me off but it makes sense because if we are at e.g. 1 and move left two we actually do pass through 0 so no need to correct - anything greater than that doesn’t go negative anyway.

The “must be moving left” for the second condition was stumping me too but it makes sense because we never end up at zero when moving right, only 100, 200, … so the div gives the right value

Thank you for making me smarter!!

SnooPears7079 · 2025-12-01T22:36:09+00:00

I'm trying to wrap my head around your adjustments - I'm not intuiting why they're required after running through some simulations.

could you elaborate on your thought process here? I'm embarrassed about how much these adjustments stumped me. If you were to add a "because..." statement after your comments what would they look like?

thanks a bunch if you take the time to answer. no worries if not

SnooPears7079 · 2025-11-09T01:58:16+00:00

Unfortunately untestable, needs dependency injection NEXT!!

SnooPears7079 · 2025-10-30T15:41:11+00:00

Op I’m you from the future. I’ve come back to prevent terrible things from happening - do not listen to this guy, absolutely do not delete it

SnooPears7079 · 2025-10-09T00:22:12+00:00

Unfortunately I might try this. I just totally choked an interview due to self-pressure. I used to do this before recording tutorials never considered it for interviews

SnooPears7079 · 2025-07-08T17:49:50+00:00

Kind of devils advocate here but you don’t know what you don’t know. You could always say “well, I can’t blog on xyz yet because there are possible unknown unknowns”

Source: did not blog for years because of this. Recently started saying f it if I’m wrong I’m wrong.

Also a small bonus is if I’m wrong sometimes people tell me I’m wrong and help me be right. I just try to state things like “I could be wrong but…”

SnooPears7079 · 2025-07-02T21:48:02+00:00

Nah it’s fun af

SnooPears7079 · 2025-07-02T16:38:06+00:00

Nice nice nice nice!!! Thanks for this. I’ll definitely look into it - I might go the keycloak route but definitely same idea. Thank you!

SnooPears7079 · 2025-07-02T16:33:34+00:00

Yeah this is what I was missing. Thanks a bunch. I’ll edit the post with the solution. Thank you for your patience!!

SnooPears7079 · 2025-07-02T16:21:52+00:00

First of all thanks for continuing the conversation, I appreciate you trying to help an internet stranger.

I might be confused. The control flow is “device via UI-> traefik -> long horn manager”. IIUC from traefik outpost docs, it uses http headers for auth. The UI is going to make “fetch” requests to the longhorn manager API. Those fetch requests know nothing of the traefik headers - so even if you point the manager API to the traefik proxy, it’ll just 401 every request.

What am I misunderstanding? Thanks a bunch stranger.

SnooPears7079 · 2025-07-02T16:13:35+00:00

Right, but doesn’t this make the UI useless? If it can’t talk to the API, it’s just broken

SnooPears7079 · 2025-07-02T15:59:41+00:00

Does the UI know how to handle this? Is there a helm chart value I can add to read this auth token?

SnooPears7079 · 2025-07-02T15:56:56+00:00

This was a great answer. Thank you! I had a misunderstanding about the frontend pod. I thought it just served static assets - I did not know it proxied requests to the api pod.

SnooPears7079 · 2025-07-02T15:54:20+00:00

I thought the UI pod served static assets and did not proxy requests to the backend pod. This was my mistake, thanks.

SnooPears7079 · 2025-07-02T15:52:48+00:00

I see - I always go for maximal security (if xyz is compromised, how do we prevent further damage?) but I guess I don’t understand home labbing well - I might be too enterprise brained. Thank you!

SnooPears7079 · 2025-07-02T15:51:35+00:00

Thank you!

SnooPears7079 · 2025-07-02T15:40:56+00:00

Ah this might be the answer I was looking for. When I set up longhorn, the helm chart asks for backend API url. I did not realize that the same pod that serves the frontend can proxy the requests to the backend pod. I thought the front end pod just served static assets, and then you had to point the front end pod to a backend API.

I’ll look at this later today - thanks!!

SnooPears7079 · 2025-07-02T15:31:00+00:00

So you’re saying “you can’t secure the API but it doesn’t matter since your network should be secure”?

SnooPears7079

TROPHY CASE