[CodexVeritas]

HttpApiKeyFilter only looked at records from the httpx logger, and it dropped them. Any other logger that prints a request URL still wrote API keys to the console and to CustomLogger's log files.

How this was found: a SerpApi key reached the log files through a Google Trends seed source in metaculus_ai_sdk, which logs the httpx error message (that message includes the full request URL). The SDK side is fixed in Metaculus/metac-ai-sdk#212.

What changes:

• The filter now rewrites every record. It replaces the values of query parameters named *key, *token, *secret, *signature or password with REDACTED, in:
  • the formatted message (format arguments included);
  • exception text;
  • stack info.
• httpx request lines are kept, with the key redacted, instead of being dropped.
• The filter never raises. A log call with mismatched format arguments is left for emit() to report, as before. (A filter runs outside Handler.handleError, so raising there would crash the caller.)
• Exception text is only overwritten when it actually contained a secret, so handlers with a custom formatException keep their own formatting.

Not covered (out of scope): secrets outside URL query strings, such as Authorization headers or api_key='…' in kwargs reprs.

Tests: 8 new unit tests in code_tests/unit_tests/test_util/test_custom_logger.py:

• the SerpApi-style warning from a non-httpx logger;
• a key passed as a format argument;
• a key inside a logged exception's text;
• httpx request lines;
• ordinary URLs left unchanged;
• token, secret and signature parameters;
• malformed format arguments;
• tracebacks without secrets.

Full unit suite: the same 14 failures on unmodified origin/main and on this branch, in test_run_bots and test_forecast_report. They're unrelated and pass when those files run alone.

🤖 Generated with Claude Code