Skip to content

synchronization: log per-event partial delivery errors from PublishBatch#22998

Draft
pkcll wants to merge 1 commit into
developfrom
chipingress-partial-delivery-cl-nodes
Draft

synchronization: log per-event partial delivery errors from PublishBatch#22998
pkcll wants to merge 1 commit into
developfrom
chipingress-partial-delivery-cl-nodes

Conversation

@pkcll

@pkcll pkcll commented Jul 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • chip_ingress_batch_worker.Send was discarding the PublishBatch response (_, err := ...).
  • Now captures resp and iterates resp.GetResults(): any result with a non-nil Error is logged at WARN with event_id, error_code, reason, telemType, and contractID, and counted in TelemetryClientMessagesDropped.
  • This implements AC Features/encode bytes32 #4 from INFOPLAT-13901: inspect other PublishBatch call sites and surface partial-delivery errors.

Jira: INFOPLAT-13901 | Epic: INFOPLAT-7177

Depends on chainlink-common PR #2210 (beholder partial delivery logging) merging first, then a go.mod bump before this PR is ready to merge.

Changes

  • core/services/synchronization/chip_ingress_batch_worker.go: capture resp, iterate resp.GetResults() for per-event errors.
  • core/services/synchronization/chip_ingress_batch_worker_test.go: TestChipIngressBatchWorker_Send_PartialDelivery — verifies partial delivery code path runs without panic and logs the WARN.

Test plan

  • go test ./core/services/synchronization/... -count=1 passes
  • TestChipIngressBatchWorker_Send_PartialDelivery passes (verifies WARN log with event_id, error_code, reason)
  • After go.mod bump: re-run to confirm no regressions from chainlink-common dep update

@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

✅ No conflicts with other open PRs targeting develop

@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

  • #added For any new functionality added.
  • #breaking_change For any functionality that requires manual action for the node to boot.
  • #bugfix For bug fixes.
  • #changed For any change to the existing functionality.
  • #db_update For any feature that introduces updates to database schema.
  • #deprecation_notice For any upcoming deprecation functionality.
  • #internal For changesets that need to be excluded from the final changelog.
  • #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
  • #removed For any functionality/config that is removed.
  • #updated For any functionality that is updated.
  • #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

@trunk-io

trunk-io Bot commented Jul 1, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic BadgeStatic Badge

Failed Test Failure Summary Logs
Test_CCIP_TokenTransfer_BnM_Aptos2EVM Logs ↗︎
Test_CCIP_TokenTransfer_LnR_without_TransferRef_Aptos2EVM Logs ↗︎
Test_CCIPTokenTransfer_Sui2EVM_BurnMintTokenPool_WithAllowlist_AfterSignerAdded Logs ↗︎
Test_CCIP_AptosMessageHasher_OnChainVerification Logs ↗︎

... and 17 more

View Full Report ↗︎Docs

@pkcll pkcll force-pushed the chipingress-partial-delivery-cl-nodes branch 2 times, most recently from 55ced63 to 32d3c31 Compare July 2, 2026 22:07
- chip_ingress_batch_worker.Send was discarding the PublishBatch response.
- Now inspects resp.GetResults(): per-event errors are grouped by error
  code and emitted as one WARN per batch ("dropped", "by_code").
- Adds chip_ingress_partial_delivery_dropped Prometheus counter with
  telemetry_type and error_code labels so dashboards and alerts can track
  rejection types without relying on logs.

Jira: INFOPLAT-13901
@pkcll pkcll force-pushed the chipingress-partial-delivery-cl-nodes branch from 32d3c31 to 094609f Compare July 2, 2026 22:18
@cl-sonarqube-production

Copy link
Copy Markdown

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