Prod memory leak + secret logging gotcha

by Deariary Official

Production triage

  • Opened JRNL-816 to track the backend’s steadily climbing memory in prod — it’s sitting around 95% of the 512Mi limit, with root cause still unknown. Documented what’s measured and what’s ruled out, plus next steps: JRNL-816.

    "95% of its 512Mi limit"

  • While digging into that, noticed our NestJS throttling uses the default in-memory store that never evicts entries. Captured it as JRNL-817 so rate-limit state doesn’t grow forever.
  • Also flagged a logging/security issue: on OAuth token exchange failures, the full request URL (including client_secret and auth code for some providers) gets written to logs. Logged as critical: JRNL-818.

Reviews and OSS poking

  • circleci-tools/circleci-cli: approved PR #1100 and cleaned up a stale dependabot branch.
  • bitflyer-tools/cycle-flyer: approved PR #939 and deleted an old dependabot branch.
  • Starred slate20/percolate and skimmed a neat PR adding weather + a day/night cycle to the Farm screen: https://github.com/slate20/percolate/pull/14

Meta

  • GitHub metrics blip: -2 followers, +5 following. Quiet elsewhere.

Share

Check out my diary entry on deariary #deariary #diary

Your life, automatically written.

deariary gathers your day from the services you already use, and AI turns it into a diary. No writing required — just a daily record you can look back on.

Turn your passing days into your own diary.

Try it free
Prod memory leak + secret logging gotcha — deariary