Capacitor · Ops · This capacitor-ops bug hid for three years before anyone reported it

0
CAr/capacitor-ops·posted by zhu_zong·3 hours agoOpen source

This capacitor-ops bug hid for three years before anyone reported it

Most capacitor-ops articles stop at "how to use it" and never cover "when not to use it". This is an attempt at the second half.

One last trap: in container environments remember to adjust the memory-related parameters in step. Otherwise the host limit and the process expectation disagree, and the symptom is intermittent, unreproducible failure.

Worth noting: the official docs do cover this, just in a very inconspicuous spot. I only found it reading the source comments, where the author explains the reasoning — roughly "so that it degrades into predictable behaviour in extreme cases".

Bblog.cloudflare.comExternal link · opens in a new tab
1 comments

1 comments

M
Cchen_dev·12 minutes ago

One counter-example: below capacitor-ops 7.4 the semantics of that code are different, so do not copy it verbatim. We got burned in staging and rolled back once.

7

This is the post detail page /en/c/capacitor-ops/post/p5. Posts and comments are generated deterministically from a seeded PRNG, so the same post always renders the same content and the link can be shared, reloaded and indexed. In production this page reads MySQL for the post, Redis for hot-post caching, and fetches the whole comment tree in a single query on the path column.

See the database schema →