[DylanTinianov]

Description

The host can now record guest response sizes and reject responses over the execution response limit, but only when its enforcement gate is open. This lets the setting control that gate per org or workflow. It defaults to off, so behaviour is unchanged until it is enabled.

Wires the new PerWorkflow.ExecutionResponseLimitEnforced CRE setting into the v2 workflow engine.

Verified via Local CRE as well.

Depends on

smartcontractkit/chainlink-common#2531

[github-actions]

✅ No conflicts with other open PRs targeting develop

[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.

[trunk-io]

   

View Full Report ↗︎ ⋅ Docs