Skip to content

fix(price-pusher): restore info level for EVM success log#3918

Closed
aditya520 wants to merge 1 commit into
mainfrom
fix/price-pusher-restore-success-log
Closed

fix(price-pusher): restore info level for EVM success log#3918
aditya520 wants to merge 1 commit into
mainfrom
fix/price-pusher-restore-success-log

Conversation

@aditya520

@aditya520 aditya520 commented Jul 21, 2026

Copy link
Copy Markdown
Member

What

Restores one line in apps/price_pusher/src/evm/evm.ts from logger.debug back to logger.info.

-          this.logger.debug({ hash }, "Price update successful");
+          this.logger.info({ hash }, "Price update successful");

Why

main is red. @pythnetwork/price-pusher#test:unit fails with 3 failures in src/evm/__tests__/receipt-tracking.test.ts (run 29835506529).

#3915 downgraded ~20 noisy log lines from info to debug. Most are fine, but this one is load-bearing, as the comment directly above it notes:

Keep one non-debug hash line per landed tx: the bundled Grafana "Tx Hash" panel scrapes this message from Loki and extracts {{.hash}}.

Pushers run at the default log-level: info (options.ts:72) and nothing in the deployments repo overrides it, so at debug the line is never emitted in production and that panel goes dark on every EVM chain.

The test failures follow from the same thing. receipt-tracking.test.ts is the regression suite for the bounded-receipt-tracker fix (#3885), and it uses this log as the observable signal that a tx was detected as landed. The same-nonce escalation case, for example, uses it to prove the original tx's tracker was not cancelled when the old tx wins the mempool race.

Test

pnpm run test:unit in apps/price_pusher: 21/21 passing, 2 suites green. Was 18 passed / 3 failed before.

Note for reviewers

#3915 also bumped price_pusher to 12.0.0. If that image has already rolled out, the Tx Hash panel is dark right now and this fix needs its own bump and deploy rather than just a merge. I left the version alone here to keep the diff to the revert.

🤖 Generated with Claude Code


Open in Devin Review

#3915 downgraded the "Price update successful" line from info to debug.
Pushers run at the default log-level of info and no deployment overrides
it, so the line is never emitted in production. That breaks the bundled
Grafana "Tx Hash" panel, which scrapes this message from Loki to extract
{{.hash}}, and it fails 3 tests in receipt-tracking.test.ts that use the
log as the signal a tx was detected as landed.

Restores the single line. The other log downgrades in #3915 are
unaffected.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Jul 21, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

7 Skipped Deployments
Project Deployment Actions Updated (UTC)
api-reference Skipped Skipped Jul 21, 2026 3:40pm
component-library Skipped Skipped Jul 21, 2026 3:40pm
developer-hub Skipped Skipped Jul 21, 2026 3:40pm
entropy-explorer Skipped Skipped Jul 21, 2026 3:40pm
insights Skipped Skipped Jul 21, 2026 3:40pm
proposals Skipped Skipped Jul 21, 2026 3:40pm
staking Skipped Skipped Jul 21, 2026 3:40pm

Request Review

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 potential issue.

Open in Devin Review

// Keep one non-debug hash line per landed tx: the bundled Grafana
// "Tx Hash" panel scrapes this message from Loki and extracts {{.hash}}.
this.logger.debug({ hash }, "Price update successful");
this.logger.info({ hash }, "Price update successful");

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Published package changed without a version bump

The price-pusher package is modified (evm.ts:498) but its published version stays at 12.0.0, which the repository's contribution rules forbid when changing a published package.
Impact: Release tooling and image consumers can't distinguish this fixed build from the previous broken one, so the fix may never be picked up or deployed as a new version.

SemVer bump requirement in AGENTS.md

AGENTS.md states: "bump package versions per SemVer when changing a published package." apps/price_pusher/package.json still declares "version": "12.0.0", the same version shipped by the earlier change that introduced this regression. Since this is a bug fix to a published package, the version should be bumped (e.g. to 12.0.1). The PR description explicitly acknowledges leaving the version unchanged.

Prompt for agents
The price_pusher package (apps/price_pusher/package.json) is a published package currently at version 12.0.0, which is the same version that shipped the logging regression this PR fixes. Per AGENTS.md ("bump package versions per SemVer when changing a published package"), this bug-fix change requires a patch version bump. Update the version field in apps/price_pusher/package.json to 12.0.1 (or appropriate SemVer) so the fixed build is distinguishable and can be released/deployed.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@aditya520

Copy link
Copy Markdown
Member Author

Superseded. The team wants the noisy logs gone, so the fix belongs in the tests rather than reverting the log level.

@aditya520 aditya520 closed this Jul 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant