Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[KS-194] Send Streams reports to TriggerService #13203

Merged
merged 2 commits into from
May 15, 2024

Conversation

bolekk
Copy link
Contributor

@bolekk bolekk commented May 15, 2024

No description provided.

Copy link
Contributor

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.

// NOTE: Skipping fields derived from FullReport, they will be filled out at a later stage
// after decoding and validating signatures.
}
return mt.triggerCapability.ProcessReport([]capMercury.FeedReport{converted})
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are assuming this is async/non-blocking?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, non-blocking in a networking sense. It only saves the report in a local map under lock - implementation here: https://github.com/smartcontractkit/chainlink-common/blob/main/pkg/capabilities/triggers/mercury_trigger.go#L82

@bolekk bolekk enabled auto-merge May 15, 2024 16:50
@bolekk bolekk added this pull request to the merge queue May 15, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 15, 2024
@bolekk bolekk added this pull request to the merge queue May 15, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 15, 2024
@bolekk bolekk added this pull request to the merge queue May 15, 2024
Merged via the queue into develop with commit 0ea99be May 15, 2024
106 of 107 checks passed
@bolekk bolekk deleted the feature/KS-194-send-trigger-events branch May 15, 2024 18:47
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.

None yet

3 participants