PixelsTech

A place for programmers
程序员自留地

[PixelsTech @PixelstechNet]

How Go Context Cancellation Actually Propagates, and Where It Stops
https://t.co/tpEqAwGdFh

[PixelsTech @PixelstechNet]

for ppl caring abt cost can read

[ImportStatic @ImportStatic]

Full write-up: https://t.co/2oMSj8r9oN

[Pi Ke @pike0000]

I have built lots of websites, apps, browser extensions, I find the most difficult problem is not to build the product but to promote it. To promote and learn how people react to my product, I need to collect data from many different sources like hacker news, reddit, X, bluesky... So I build an service to track my product and put them all together and I then have a consolidated place to know what's going on with it. This ends with an open source project which I think would benefit others. Also you can contrinute to add more sources and give feedback on what can be improved.

The service is self-hosted and all you APi keys and AI keys are saved on your machine, so safe to use.

The repo: https://t.co/6aLn6qwHrT

[PixelsTech @PixelstechNet]

Go 1.27.3 and 1.26.10 reject any chain through 16 revoked eMudhra intermediates.

Go Weekly, 2026-10-19 ~ 2026-10-26: 44 posts. 4 worth your time:

1. Go's method must have no type parameters error usually means an old toolchain or go line, unless it is an interface. The post includes real output from Go 1.25, 1.26, and 1.27 to help diagnose it.

2. CVE-2026-111497 is in Brotli's C decoder. The post maps which Go and Rust stacks link it, which frameworks decode br request bodies by default, and the versions to check.

3. A Go SQLite benchmark found mattn/go-sqlite3 ran point queries 1.6x faster than https://t.co/mtiObYaPTZ, but its Linux cross-build from a Mac was a stub. That trade-off matters when choosing a driver.

4. In package APIs, each %w makes the wrapped error part of your API. The post covers when to use sentinels, typed errors, %v, and where to log.

All 44 links, grouped by topic:
https://t.co/bEfCEhUAZV

[PixelsTech @PixelstechNet]

more on https://t.co/9K85ateFzM

[PixelsTech @PixelstechNet]

Node.js 26 becomes Active LTS on October 28, 2026, and teams on Node 22 or 24 should plan to move directly to 26 because Node 22 support ends in April 2027 while 26 lasts until April 2029. The main breakage includes removed response.writeHeader(), _stream_* modules, --experimental-transform-types, and short AES-GCM tags without an explicit authTagLength; module.register() and passing CryptoKey to crypto functions are runtime-deprecated, native addons need rebuilding for NODE_MODULE_VERSION 147, and outbound HTTP code should be retested against undici 8. Skipping Node 25 means also inheriting the removal of bundled Corepack, fs.F_OK/R_OK/W_OK/X_OK constants, and SlowBuffer, plus default Web Storage globals and changed localStorage behavior when no storage file is configured. Before upgrading, run the full test suite with --throw-deprecation, since warnings can fire asynchronously after a test appears to pass, and use a text audit for known patterns, then check dependencies and native modules and apply the official codemods for fs constants and SlowBuffer. The payoff includes Temporal enabled by default and V8 14.6 features such as Map.prototype.getOrInsert(), but verify your own suite on Node 26.12.0 or the first 26.x LTS build before production.

[PixelsTech @PixelstechNet]

@Yuchenj_UW apprecitae the directness here

[PixelsTech @PixelstechNet]

Zomato cut Go GC CPU from about 25% to under 2% by setting GOMEMLIMIT to 90% of each container's memory ceiling, saving roughly $30K monthly.

Go Weekly, 2026-10-12 ~ 2026-10-19: 32 posts. 5 worth your time:

1. A Go save function using defer f.Close() and defer w.Flush() returned nil while leaving 8 KiB of a 20 KB file. The post explains why the Close error matters and what to write instead.

2. https://t.co/cQTzEOdT66 and https://t.co/1TZZnMqLAR return false when you wrap &MyErr{} but check for MyErr. Go 1.27 adds a vet check that catches it, and the post covers the fix.

3. Go 1.27 includes an HTTP client change that can make programs sending many sequential HTTP/1 requests significantly faster. This is useful for connection-reuse-heavy workloads.

4. Go 1.27 drains an unread HTTP/1 response body on Close. Tests cover chunked streams, slow bodies, json.Decoder and forced closes to see which connections get reused.

5. gopls adds interactive LSP refactoring for struct tags, interfaces, and declaration moves. That gives Go developers more automated refactors directly in the editor.

All 32 links, grouped by topic:
https://t.co/Imp7MqfdCN

[PixelsTech @PixelstechNet]

more details at https://t.co/X8kyXvO6T4

[PixelsTech @PixelstechNet]

Python 3.15 enables UTF-8 mode by default via PEP 686, so bare open() calls, stdio, pipes, command-line arguments, environment variables, and filenames use UTF-8 instead of the locale encoding. The change mostly breaks Windows code that wrote files with the ANSI code page, since those files may now raise UnicodeDecodeError or decode as mojibake when read back. Developers can preview the behavior on Python 3.14 with -X utf8 or PYTHONUTF8=1 and find implicit encoding sites using -X warn_default_encoding, PYTHONWARNDEFAULTENCODING, or Ruff's PLW1514 rule. Fix flagged calls by passing encoding="utf-8" for new or exchanged data, the correct legacy encoding such as cp1252 for existing Windows files, or encoding="locale" when system settings are truly required, and remember to set encodings on subprocess pipes when using text=True. PYTHONUTF8=0 or -X utf8=0 can temporarily restore old behavior, but explicit encoding arguments are the durable cross-version fix.

[PixelsTech @PixelstechNet]

Full write-up with the code: https://t.co/g4PNr35Gds

[PixelsTech @PixelstechNet]

Anthropic's new Scion does every commit on the server, which sounds like Subversion again. Google's Piper was already taking 60,000 to 70,000 commits a workday; Anthropic is at 30,000 a day.

[PixelsTech @PixelstechNet]

Good news, our smart redact PDF tool now supports in-browser AI processing to better find information to redact. Give a try. https://t.co/Q5SgoVMJuf

[PixelsTech @PixelstechNet]

Upgrading to Go 1.27 made default gzip 3 to 12x faster, and its output up to 13% bigger.

That's 1 of 11 behaviors that changed in code nobody touched.

Go Weekly, Oct 5–12: 58 posts. Five worth your time:

1. Go 1.27.2 fixes a compiler bug that the race detector hides: a pointer that reads garbage. The same patch also fixes three JSON regressions and inflated coverage numbers.

2. In tests with t.Parallel subtests, defer can run before the subtests finish. Use t.Cleanup instead: it runs in LIFO order and respects the test lifecycle.

3. Go 1.27 adds a uuid package to the standard library, covering v4, v7 and parsing. You may be able to drop google/uuid, though it still does a few things the stdlib version doesn't.

4. Still choosing an HTTP router? Ben Hoyt compared the approaches and concludes the Go 1.22 stdlib router is now the recommended choice.

5. connect-go v2 is out: simpler APIs, pluggable transports, and v1 and v2 can coexist during migration.

All 58 links, grouped by topic:
https://t.co/3gFmqVukxp

[PixelsTech @PixelstechNet]

Full write-up with the code: https://t.co/aujFWWpvB6

[PixelsTech @PixelstechNet]

SQLite 3.54.0: updating a JSON document without touching its two json_extract-indexed fields wrote 1 WAL page per UPDATE, down from 3. Plain-column and STORED-column indexes still get rewritten.

[PixelsTech @PixelstechNet]

sql.Null[[]int64] still fails with pgx 5.11 on Go 1.27. sql.Null is a sql.Scanner, so the array never reaches pgx and we got the old "unsupported Scan" error. A NULL array passes, real data doesn't. Scan into a plain []int64 (nil for NULL) instead.

[ImportStatic @ImportStatic]

We ran 21 access checks under six macOS sandbox profiles. Blocking writes and all network left ~/.ssh readable in every one, and a five-entry credential deny list still missed the GitHub CLI token. https://t.co/Ry6tsxaIrG

[PixelsTech @PixelstechNet]

@AnthropicAI Enrolment is a PR to Anthropic's GitHub repo, and eligibility follows OSS-Fuzz's "critical impact" test. No human reviews the reports, so double-check severity before filing CVEs.

[PixelsTech @PixelstechNet]

If you maintain a widely used open-source project, Anthropic will now scan it for vulnerabilities for free. Reports include a reproducer and sometimes a patch, but no human review, so treat the severity rating as a first guess.
https://t.co/NAw6vWopHT