frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Unauthenticated remote code execution in Nginx

https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
786•speedping•5h ago•329 comments

Seven new models at scalable price-performance

https://microsoft.ai/news/microsoft-ignite-2026/
331•gmays•4h ago•216 comments

Inside Deutsche Bank

https://www.inside-db.com/
409•gyre007•5h ago•145 comments

DNS resolvers are the wrong place to fight piracy

https://techstackups.com/articles/quad9-leaves-france-dns-blocking/
484•ritzaco•7h ago•168 comments

AI agents ask better questions than KPMG accountants in audit trial

https://europeanbusinessmagazine.com/ai-agents-better-questions-kpmg/
193•Betelbuddy•5h ago•100 comments

DaisyRose-27B: 1,200-task RL took Qwen3.8 from 5.6% to 12% on Terminal-Bench 4.1

https://www.radixark.com/blog/daisyrose-27b
30•de_sty•1h ago•4 comments

Genie 4 is now available

https://blog.google/innovation-and-ai/models-and-research/google-deepmind/genie-4-now-available-p...
112•leumon•2h ago•89 comments

The Magic of Partial Evaluation

https://jimmyhmiller.com/magic-of-partial-evaluation
56•aray07•2h ago•5 comments

Search Browser – Minimalist WebKit browser with Chrome extension support

https://searchbrowser.app/
19•rsaz•55m ago•6 comments

Advancing chip design with OpenAI models

https://openai.com/index/advancing-chip-design-with-our-models/
80•vighneshiyer•3h ago•36 comments

The Cambridge Dictionary has named ‘human’ as the Word of the Year 2026

https://www.cam.ac.uk/news/cambridge-dictionary-reveals-word-of-the-year-2026
191•DeepLogin•6h ago•145 comments

KVM: x86: Unconditionally reset MMU context when emulating INIT (CVE-2026-99312)

https://www.cve.org/CVERecord?id=CVE-2026-99312
150•Kozmik1•4h ago•97 comments

Show HN: Mastra Factory, the open-source software factory we use to build Mastra

55•codekarate•4h ago•16 comments

The First Revolver: How We Got from Blackbeard's Six Pistols to the Six-Shooter

https://americanhandgunner.com/handguns/revolvers/the-first-revolver/
30•bushwart•3d ago•8 comments

Show HN: ExitPath – Open-source ways out of Slack, Notion and Microsoft 365

https://exitpath-ruddy.vercel.app/
101•zerocool0101•4h ago•19 comments

Show HN: Take Voyager 1 apart, down to a single memory chip

https://rshekhar.com/voyager/
101•raj-shekhar•4h ago•24 comments

Show HN: Nobody blocks a keyboard – Rooted Android as a physical USB Deck

https://github.com/mr-anjaneyam/Emittr
34•mr-anjaneyam•2d ago•37 comments

F-22 Next-Generation micro–Data Transfer Cartridge (mDTC)

https://sam.gov/workspace/contract/opp/8948e8601e964c6aba9c801eee16b1be/view
122•birdboat00•5h ago•77 comments

The x86 CPU: From 4004 to 486

https://pikuma.com/blog/history-of-x86-4004-to-486
111•ibobev•6h ago•30 comments

CrossPoint Reader

https://crosspointreader.com
55•kristianpaul•3h ago•25 comments

When Free Software Isn't Free Enough

https://foss.life/notes/2026/free-software-isnt-free-enough/
21•hn_acker•2h ago•2 comments

Launch HN: Maritime (YC F26) – A managed cloud for production AI agents

29•ashriv•3h ago•25 comments

A live service duress prototype

https://github.com/Ymsniper/vault-share
6•Ymsniper•3d ago•0 comments

Evidence (YC S21) Is Hiring

https://www.ycombinator.com/companies/evidence/jobs/1xb9PpP-founding-gtm-lead
1•amcaskill•8h ago

Sexp Matrix

https://lisper.cc/ideas/entangle.html
7•todsacerdoti•58m ago•1 comments

A Primer on Fourier Series (2025)

https://arxiv.org/abs/2510.18203
84•teleforce•6h ago•21 comments

Energy-Based Reasoners: 385x more efficient inference

https://energy-based-reasoners.github.io/
284•frenchmajesty•11h ago•44 comments

Lakegres: Vector search on existing Open/Hudi/Iceberg tables

https://www.onehouse.ai/blog/lakegres-vector-search-on-open-table-formats
33•cloud8bits•3h ago•6 comments

Google Gemini's "Tasks" Personal Assistant Is Now Free

https://blog.google/innovation-and-ai/products/gemini-app/tasks-in-gemini-free-new-features/
5•hackeratrandom•39m ago•2 comments

SuperEMeans: Making e-means 3× faster

https://www.lkuffo.com/superemeans/
42•lkuffo2•4h ago•0 comments
Open in hackernews

Production tests: a guidebook for better systems and more sleep

https://martincapodici.com/2025/05/13/production-tests-a-guidebook-for-better-systems-and-more-sleep/
78•mcapodici•1y ago

Comments

ashishb•1y ago
Here's a general rule that I follow along with this and that is "write tests along the axis of minimum change"[1]. Such tests are more valuable and require less maintenance over time.

1 - https://ashishb.net/programming/bad-and-good-ways-to-write-a...

compumike•1y ago
I'd add that, in terms of tactical implementation, production tests can be implemented at least two different ways:

(1) You set up an outside service to send an HTTP response (or run a headless browser session) every minute, and your endpoint runs some internal assertions that everything looks good, and returns 200 on success.

(2) You set up a scheduled job to run every minute internal to your service. This job does some internal assertions that everything looks good, and sends a heartbeat to an outside service on success.

For #2: most apps of any complexity will already have some system for background and scheduled jobs, so #2 can make a lot of sense. It can also serve as a production assertion that your background job system (Sidekiq, Celery, Resque, crond, systemd, etc) is healthy and running! But it doesn't test the HTTP side of your stack at all.

For #1: it has the advantage that you also get to assert that all the layers between your user and your application are up and running: DNS, load balancers, SSL certificates, etc. But this means that on failure, it may be less immediately clear whether the failure is internal to your application, or somewhere else in the stack.

My personal take has been to lean toward #2 more heavily (lots of individual check jobs that run once per minute inside Sidekiq, and then check-in on success), but with a little bit of #1 sprinkled in as well (some lightweight health-check endpoints, others that do more intense checks on various parts of the system, a few that monitor various redirects like www->root domain or http->https). And for our team we implement both #1 and #2 with Heii On-Call https://heiioncall.com/ : for #2, sending heartbeats from the cron-style check jobs to the "Inbound Liveness" triggers, and for #1, implementing a bunch of "Outbound Probe" HTTP uptime checks with various assertions on the response headers etc.

And this production monitoring is all in addition to a ton of rspec and capybara tests that run in CI before a build gets deployed. In terms of effort or lines of code, it's probably:

    90% rspec and capybara tests that run on CI (not production tests)
    9% various SystemXyzCheckJob tests that run every minute in production and send a heartbeat
    1% various health check endpoints with different assertions that are hit externally in production
And absolutely agree about requiring multiple consecutive failures before an alarm! Whenever I'm woken up by a false positive, my default timeout (i.e. # of consecutive failures required) gets a little bit higher :)
hugs•1y ago
yeah, full end-to-end tests/monitors are like fire alarms: they can often tell you something is wrong, but not exactly what is wrong. but that doesn't mean fire alarms have no value. most common failure mode for teams are having too many or none at all. but having a few in a few key places is the way to go.
mhw•1y ago
The fabulous blazer gem includes a feature for #2: https://github.com/ankane/blazer?tab=readme-ov-file#checks - it’s limited to checks that can be expressed as SQL queries, but that can get you quite a way
aleksiy123•1y ago
At Google we call these probers.

Does anyone know of any tools/saas that do this.

Was thinking it may be a good potential product.

Especially if it was super easy to generate/spin up for side projects.

hugs•1y ago
"testing in production" can be controversial, but this is a well-balanced take on it.

lately i've been working on a decentralized production testing network called 'valet network' [1] (full-disclosure: selenium creator here)

i suspect production tests are the killer app for this kind of network: test any site on a real device from anywhere on idle devices that more closely match real world conditions, but as mentioned in the article, it's not that simple. dev users will still need to be smart about creating test data and filtering out the tests from system logs. i'm still in the "is this something people want?" learning phase, even though this is definitely something i want and wish i had when i was helping to fix healthcare.gov back in 2013/2014.

[1]: https://gist.github.com/hugs/7ba46b32d3a21945e08e78510224610...

vasusen•1y ago
Thank you for the balanced take on an extremely spicy topic.

At WePay (YC S09) we debated this extensively and came up with a similar middle of the way solution. Making sure that a credit card can get tokenized is the critical flow and should run every minute. We ended up with about 4-5 very quick production tests. They helped with debugging as well as alerting.

I am now building a full, automated testing solution at Donobu (https://www.donobu.com), and production tests definitely come up as their own subcategory of e2e tests. I am going to use your guidelines to refine our prompt and bound our production test generator.

testthetest•1y ago
> Running a test every minute, or 1440 times a day, will show up quite a lot in logs, metrics, and traces.

...not to mention that automated tests are by definition bot traffic, and websites do/should have protections against spam. Cloudflare or AWS WAF tends to filter out some of our AWS DeviceFarm tests, and running automated tests directly from EC2 instances is pretty much guaranteed to be caught by Captcha. Which is not a complaint: this is literally what they were designed to do.

A way to mitigate this issue is to implement "test-only" user agents or tokens to make sure that synthetic requests are distinguishable from real ones, but that means that our code does something in testing that it doesn't do in "real life". (The full Volkswagen effect.)

burnt-resistor•1y ago
Also known as deep monitoring: checking that functionality is available and working correctly.