Skip to content

Add Stellar data feeds write e2e - #23412

Draft
Fletch153 wants to merge 6 commits into
developfrom
feature/DF-25510/stellar-data-feeds-e2e
Draft

Add Stellar data feeds write e2e#23412
Fletch153 wants to merge 6 commits into
developfrom
feature/DF-25510/stellar-data-feeds-e2e

Conversation

@Fletch153

@Fletch153 Fletch153 commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • End to end test proving the CRE write path into the Stellar data feeds cache: a workflow DON produces a signed report, the Soroban forwarder verifies it, the cache stores the answer, and the test reads it back through the generated bindings.
  • Adds a data feeds write workflow module, cache deploy and configure helpers in the stellar feature, and a fourth subtest in the stellar suite.

- Pin chainlink-stellar and bindings to the embedded artifacts commit
- Deploy and configure the data feeds cache via the stellar feature
- New datafeeds/write workflow encoding report entries in-workflow
- Assert the answer lands on-chain by polling the cache latest_round
- Bump chainlink-stellar and bindings pins to the regenerated
  batch bindings in all four modules
- Data ids are now 32 opaque bytes: widen the feature helpers
  and the test fixture, drop the wire-id zero padding
- Read via batch LatestRound and unwrap the single entry
@Fletch153
Fletch153 force-pushed the feature/DF-25510/stellar-data-feeds-e2e branch from b5e09b0 to 9ef3eda Compare August 18, 2026 19:02
- Guard a zero scheduled execution time, which the cache would
  silently drop as stale, and split the data id hex errors so
  the length case no longer prints a nil decode error
- Return an error for a missing forwarder instead of panicking
- Fold the vestigial error-message block onto the proto getter
- Assert round id and timestamp alongside the answer
- Rename helpers to package conventions, drop restating doc
  comments, convert report tests to require
…tellar-data-feeds-e2e

# Conflicts:
#	core/scripts/go.mod
#	core/scripts/go.sum
#	deployment/go.mod
#	deployment/go.sum
#	system-tests/lib/go.mod
#	system-tests/lib/go.sum
#	system-tests/tests/go.mod
#	system-tests/tests/go.sum
@github-actions

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.

@github-actions

Copy link
Copy Markdown
Contributor

✅ No conflicts with other open PRs targeting develop

- Suppress gosec G115 on the intentional bit-preserving
  int64 to uint64 conversions
- Mark the report tests parallel
@trunk-io

trunk-io Bot commented Aug 18, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

The bindings branch replaced the embedded data feeds cache WASM
with the amd64 build the check-generated gate verifies; move all
four module pins to that tip so the e2e deploys the same bytes.
@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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant