ChIP DurableEmitter Integration + Testing

[DylanTinianov]

DurableEmitter

Integrates DurableEmitter with local CRE environment and core. Creates ORM for durable event storage, and verifies the emitter persists events and deletes them once accepted by Chip server.

Also adds load testing on DurableEmitter to scale TPS and payload sizes for local use only.

DurableEmitter (chainlink-common)

[github-actions]

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.

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

     

Failed Test	Failure Summary	Logs
TestScripts/node/validate/disk-based-logging-no-dir	The test failed because the logging directory was not specified, causing a logging configuration error.	Logs ↗︎
TestScripts/node/validate/disk-based-logging-no-dir	The test failed because the logging directory was not specified, causing a failure in the disk-based logging configuration.	Logs ↗︎
TestResolver_ConfigV2/partial	The test failed without a specific error message, indicating an unspecified failure during configuration validation or execution.	Logs ↗︎
TestScripts/config/merge_raw_configs	The test failed during configuration validation, likely due to an issue with the configuration file or environment setup.	Logs ↗︎

... and 34 more

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate failed

Failed conditions
18 New Major Issues (required ≤ 5)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube

Catch issues before they fail your Quality Gate with our IDE extension SonarQube IDE