Skip to content

Durable Emitter - Set publish timeout#23001

Open
tarcisiozf wants to merge 5 commits into
developfrom
durable-emitter/set-timeout
Open

Durable Emitter - Set publish timeout#23001
tarcisiozf wants to merge 5 commits into
developfrom
durable-emitter/set-timeout

Conversation

@tarcisiozf

Copy link
Copy Markdown
Contributor

This pull request introduces a configuration improvement to the event emitter setup in the NewApplication function. The most notable change is the addition of a maximum publish timeout to help prevent events from hanging indefinitely during publishing.

Event emitter configuration:

  • Set MaxPublishTimeout to 10 seconds in the durableCfg for the event emitter, ensuring that event publishing will fail if it takes longer than this duration.

@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_RegulatedTokenTransfer_Aptos2EVM Logs ↗︎
Test_CCIP_AptosMessageHasher_FuzzGeneratedCases Logs ↗︎
TestConfigPoller/LatestConfig,_when_logs_have_been_pruned_and_config_store_contract_is_configured/if_callReadConfig_succeeds The test failed during the execution of a specific configuration poller test, but the exact cause of failure is not provided. Logs ↗︎
Test_CCIP_Messaging_EVM2Aptos Logs ↗︎

... and 19 more

View Full Report ↗︎Docs

@tarcisiozf tarcisiozf marked this pull request as ready for review July 1, 2026 16:45
@tarcisiozf tarcisiozf requested review from a team as code owners July 1, 2026 16:45
@DylanTinianov DylanTinianov added build-test-image Will build the e2e test image in integration-tests workflow for PRs build-publish Build and Publish image to SDLC labels Jul 3, 2026
@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

build-publish Build and Publish image to SDLC build-test-image Will build the e2e test image in integration-tests workflow for PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants