Skip to content

Conversation

@ray-roestenburg-da
Copy link
Contributor

@ray-roestenburg-da ray-roestenburg-da commented Jun 6, 2025

Fixes #610
Fixes #464

  • Added /v2/updates
  • Updated docs
  • Updated release notes

basic cluster test passes

Pull Request Checklist

Cluster Testing

  • If a cluster test is required, comment /cluster_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
  • If a hard-migration test is required (from the latest release), comment /hdm_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.

PR Guidelines

  • Include any change that might be observable by our partners or affect their deployment in the release notes.
  • Specify fixed issues with Fixes #n, and mention issues worked on using #n
  • Include a screenshot for frontend-related PRs - see README or use your favorite screenshot tool

Merge Guidelines

  • Make the git commit message look sensible when squash-merging on GitHub (most likely: just copy your PR description).

@ray-roestenburg-da ray-roestenburg-da force-pushed the ray/v2-updates branch 4 times, most recently from 5add5c7 to 99af33d Compare June 10, 2025 20:28
@ray-roestenburg-da ray-roestenburg-da changed the title Changes to openapi for /v2/updates Added /v2/updates Jun 10, 2025
@ray-roestenburg-da ray-roestenburg-da force-pushed the ray/v2-updates branch 3 times, most recently from a0164c6 to ee97f2e Compare June 10, 2025 22:03
@ray-roestenburg-da ray-roestenburg-da marked this pull request as ready for review June 10, 2025 22:03
Comment on lines 1261 to 1271
Copy link
Contributor

Choose a reason for hiding this comment

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

This file will hit scalafmt

Copy link
Contributor Author

@ray-roestenburg-da ray-roestenburg-da Jun 10, 2025

Choose a reason for hiding this comment

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

Fixed, thanks

@ray-roestenburg-da ray-roestenburg-da force-pushed the ray/v2-updates branch 2 times, most recently from 0f4a230 to 31645ca Compare June 11, 2025 12:51
DA Automation and others added 4 commits June 11, 2025 13:02
Signed-off-by: DA Automation <splice-maintainers@digitalasset.com>
…ation/tests/ScanHistoryBackfillingIntegrationTest.scala

Co-authored-by: Stephen Compall <stephen.compall@digitalasset.com>
Signed-off-by: Raymond Roestenburg <98821776+ray-roestenburg-da@users.noreply.github.com>
Co-authored-by: Stephen Compall <stephen.compall@digitalasset.com>
Signed-off-by: Raymond Roestenburg <98821776+ray-roestenburg-da@users.noreply.github.com>
Signed-off-by: DA Automation <splice-maintainers@digitalasset.com>
Copy link
Contributor

@moritzkiefer-da moritzkiefer-da left a comment

Choose a reason for hiding this comment

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

lgtm thx

}

clue("Compare scan histories with each other using the v1 HTTP endpoint") {
// The v1 endpoint is deprecated, but we still have users using it
Copy link
Contributor

Choose a reason for hiding this comment

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

do we really want to run both endpoints at the end of every test? Seems a bit overkill

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I did not notice that this runs at the end of every test? there were versions of this for v0 and v1 so I (lazily) added v2 for some coverage

@ray-roestenburg-da ray-roestenburg-da merged commit 9d1f7e0 into main Jun 11, 2025
113 of 115 checks passed
@ray-roestenburg-da ray-roestenburg-da deleted the ray/v2-updates branch June 11, 2025 15:01
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.

Remove offset from /v1/updates In /v1/updates, order event_by_id by id in API responses instead of just serializing the map

4 participants