What a surprise. You can't append new item to existing list or create a new list with kubernetes json patch. stackoverflow.com/questions/47...
Posts by a public builder
I am fed up with all the kubernetes DSL. helm and kustomize may do the work, but I need to learn a lot to do my job. E.g. a task as simple as copy and modify existing StorageClass to support Retain ReclaimPolicy is not easily achievable to me. I need to learn a ton of the syntax and semantics.
Remember 1 hour of vibe-coding can save you 1 day of debugging.
This is what I get for upload the wrong format of file for a batch generation task. I gave up.
Gemini's batch generation api is a PITA. Some configs for normal generation (e.g. think config) are not available in batch generation. What's worse, you can pass a pillow Image.Image to generate_content, but you have to "reverse engineer" gemini source code to figure out to to serialize an Image.
Scratching head for cloudflare r2 CORS responses. Turned out there are two requests, one with Sec-Fetch-Mode: no-cors and the other with Sec-Fetch-Mode: cors. The result of the first request was cached. Today's hero community.cloudflare.com/t/problem-wi...
The magic of next.js. You are building your nextjs container image, and it will actually try to connect to your database.
Based on a true story.
Creating a PR to the repo whose code base is mostly owned by you alone.
Gee. Open telemetry and grafana cloud is really a godsend. Super easy to setup, yet extremely powerful (hope to show some dashboard porn soon, but for now, not enough data). Plus, grafana cloud is just too cheap.
My day so far.
I have a solution and I don't know why it works.
I have to confess my love for nextjs. This affection does not stem from its ease to use or unparalleled power. Having went through countless seemingly un-decipherable errors of nextjs should be a competitive edge for me. I hope nextjs would be more widely adopted. All my efforts shouldn't be in vain
For this simple task, you will need mitmproxy. How exciting!
It is 2025, and you can't see what went wrong with your CORS requests. None of the solutions in stackoverflow.com/questions/57... worked for me. Just show me the raw CORS request and response instead of a vague CORS error. God damn it.
I tried a ton of html to image libraries. None of they solve the problem "Error: CSSStyleSheet.cssRules getter: Not allowed to access cross-origin stylesheet". Most of the issues remain free-standing for quite a few years. github.com/bubkoo/html-... Alas, firefox is really not loved.
As a detective who has a lot of time bisecting, I love to solve nextjs mysteries like this. The less clues, the better.
Nextjs is really a PITA.
TIL that you need the runtime environment variable set to build a nextjs project. github.com/vercel/next....
I need to be more specific. I was using trpc for client-server communication. TRPC use zod for input/output schema (including serializing and deserializing) instead of static types. In this case, Static types + auto deriving serializer/deserializer will make the interface clearer and easier to use.
Just found out I needed github.com/fabien0102/t... to convert real types to a zod schema. Why would I want this instead of static types? Because, trpc, the End-to-end typesafe rpc framework prefers implicit types. I have to use zod for output validation! Oh my gosh.
I am horrified by typescript programmers' abuse of type inference on almost dynamic objects and functions. Can we just disband dynamic evils once and for all? Why would anyone prefer zod over real static types? Please use derive/deriving as in rust/haskell while crossing the boundary.
Here is an even uglier solution to this.
Functional programmers, guess why you have this error. One does not simply use pattern match with typescript. All you have to do is forget the good old days.
stackoverflow.com/questions/71... "Can we all agree this error message is worse than useless?!" My vibe-fu is strong enough to have the error "Hydration failed because the initial UI does not match what was rendered on the server", weak enough to not be able to ask the agent to try ~50 solutions.
The old adage of "be conservative in what you send, be liberal in what you accept" is truer in typescript. The caller of the function which returns a value of type `HttpAgentOptions | HttpsAgentOptions` has no easy way to override any http or https specific options.
Front-end developers, you deserve better. I really don't understand why typescript is so universally-beloved. How can anyone bear ugly solutions listed on stackoverflow.com/questions/14... just to check the type of an interface.
Why is the quality of popular nodejs libraries so low? I want to intercept openai traffic for debugging. proxy-agent library doesn't even have an option to use self-signed certificates. People came up with ingenious solutions, but the issue is never fixed in upstream. github.com/TooTallNate/...