LightNews — News, ranked by scholars

jacky.wtf

@jacky.wtf

Something I like about the testing libraries is Errorf and Fatalf. pkg.go.dev/testing@go1.... versus pkg.go.dev/testing@go1.... makes it possible to do assertions for multiple things but fail hard only when it's needed. Normally, you'd have to keep re-running a test to see this in Rust.

testing package - testing - Go Packages

pkg.go.dev

October 19, 2026 at 11:59 PM

Kindtech

@kindtech.bsky.social

Wrapping errors in Go preserves context as they bubble up. fmt Errorf with the percent w verb attaches a cause, and errors Is checks the chain instead of exact matches. Callers get readable messages while the original failure stays inspectable for retries. #Go #ErrorHandling #Programming

August 20, 2026 at 1:27 PM

Developers Swearing

@gitlost.net

…to get stack traces (#5139) `fmt.Errorf()` is idiomatic, but in practice sucks because we don't get stack traces. This PR switches us…

April 22, 2025 at 2:08 AM

Developers Swearing

@gitlost.net

…to get stack traces `fmt.Errorf()` is idiomatic, but in practice sucks because we don't get stack traces. This PR switches us to…

April 16, 2025 at 1:37 AM

Abdullah Durrani

@layinthegrass.bsky.social

Going through the fmt docs and stumbled on a hidden gem in the Errorf example.

Bueller?... Bueller?

😂

#golang #devlearning #BuildInPublic #ferrisbueller

June 14, 2025 at 12:17 AM

skywatch

@skywatch.bsky.social

Merged PR into main at bluesky-social/indigo: carstore: fix slog logging / Errorf wrap (#916)

January 22, 2025 at 2:42 AM

skywatch

@skywatch.bsky.social

New PR: carstore: fix slog logging / Errorf wrap (#916)

carstore: fix slog logging / Errorf wrap by bnewbold · Pull Request #916 · bluesky-social/indigo

github.com

January 22, 2025 at 2:30 AM

sodiboo :pride_heart:

@sodiboo.gaysex.cloud

anyone know what's causing this "More Actions..." to appear in vscode with fixes that introduce syntax errors? 'cause i'm 99% sure that's not clippy suggsting this. its suggestion is available as the first option. but that last option is just wrong lmao

Rust code. the end of a line says:

user_data as *mut CompositorUserData;

this expression has a pedantic lint:

`as` casting between raw pointers without changing their constness.

The vscode quick fix menu is open. It has three sections:

Quick Fix. This section contains three actions:

try `pointer::cast()`, a safer alternative: `user_data.cast::<CompositorUserData>()`

that fix is actually fully correct. this is what clippy suggests.

then there are two so-called "fixes" labeled "Fix using Copilot" and "Explain using Copilot". ew. why are they there. not in this menu please

Extract:

Extract into variable

And lastly, there are "More Actions...". This section has a single aciton, with a lightbulk icon as if it were an LSP-provided refactor:

Remove `mut` keyword

this is highlighted

here's the result of applying the aforementioned refactor.

the expression now says:

user_data as *CompositorUserData;

it is underlined in red. this is a syntax errorf

expected `mut` or `const` keyword in raw pointer type

December 3, 2024 at 10:45 PM

Prisma

@prisma.io

Error dumps cluttering your terminal?

Prisma lets you pick your error style with `errorFormat`:

`colorless` → clean, no frills (default)
`minimal` → just the essentials
`pretty` → dev-friendly and easy to scan

Try it out 👉 pris.ly/docs/errorf...

May 15, 2025 at 9:03 AM

Codigodeerror.com

@codigodeerror.bsky.social

Error F o F1 en placa de cocina AEG: qué significa y cómo actuar

¿Tu placa AEG muestra este error y no sabes por qué? Descubre las causas reales: recipiente, humedad o instalación, y qué revisar para resolverlo rápido.

#AEG #PlacaDeCocina #ErrorF #ErrorF1 #Electrodomésticos