Log Event Trigger Capability Development: Part 2

[kidambisrinivas]

Updates

• Receive log.Data as values.Value to preserve type info
• Test cursor usage of LogEventTrigger capability to ensure that old logs are not sent as duplicates and only new logs are sent in the callback channel of registered Triggers
• Add JSON schema for the capability config and output
• Generate SDK helpers

References

• Chainlink Common changes

  • Expose ContractReader and ChainWriter of relayer in relayerSet PR
  • Add LatestHead relayer method to gRPC client and server implementations
  • Support Type Aliases in values.Value pkg
    • Unwrap
      • Chainlink-common PR1: Handle type aliases in slices in bytes/unwrap
      • Chainlink-common PR2: Remove explicit handling type aliases in slices in int/unwrap and handle it in generic unwrap
      • Chainlink-common PR3: More alias handling in unwrap functionality of Value
      • Chainlink-common PR4: Support passing in a values.Value to the chainreader GetLatestValue method
    • Wrap
      • Fix alias typing and tests
      • Add array support to slice
  • Support passing in a values.Value to the ChainReader GetLatestValue and QueryKey methods
    • Chainlink-common PR
    • Chainlink core PR: Support passing in a values.Value to the GetLatestValue and QueryKey methods

• Chainlink Core changes

  • Log Event Trigger Capability Development: Part 1
  • Log Event Trigger Capability Development: Part 2
  • Log Event Trigger Capability Development: Part 3
  • Set cursor direction

SDK Generation

$ go generate ./core/capabilities/triggers/logevent/logeventcap

Testing

$ go test -count=1 -v -run="^TestLogEventTriggerEVMHappyPath$" ./core/services/relay/evm/capabilities
$ go test -count=1 -v -run="^TestLogEventTriggerCursorNewLogs$" ./core/services/relay/evm/capabilities

[github-actions]

I see you updated files related to core. Please run pnpm changeset 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.

[cl-sonarqube-production]

Quality Gate passed

Issues
1 New issue
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
8.7% Coverage on New Code
5.9% Duplication on New Code

See analysis details on SonarQube