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

flowctl: use max build_id for validating local specs #1636

Merged
merged 1 commit into from
Sep 17, 2024

Conversation

psFried
Copy link
Member

@psFried psFried commented Sep 17, 2024

The validation logic was changed in a prior commit to error if the last_build_id of a live spec is greater than the current build id. This change was supposed to go along with that, but got missed. Using the maximum id value ensures that we never get errors due to the build id being superseded.


This change is Reviewable

The validation logic was changed in a prior commit to error if the
`last_build_id` of a live spec is greater than the current build id.
This change was supposed to go along with that, but got missed. Using
the maximum id value ensures that we never get errors due to the build
id being superseded.
@psFried psFried added bug Something isn't working flowctl Issues related to the user facing CLI change:unplanned This change is unplanned, useful for things like docs labels Sep 17, 2024
@psFried psFried requested a review from jshearer September 17, 2024 13:53
@psFried psFried marked this pull request as ready for review September 17, 2024 15:02
Copy link
Contributor

@jshearer jshearer left a comment

Choose a reason for hiding this comment

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

Confirmed that this change fixes the unexpected

current build ID 0101010101010101 has been superseded by a larger build ID ...; please retry the operation

errors

@psFried psFried merged commit 9d65aa5 into master Sep 17, 2024
4 checks passed
github-actions bot pushed a commit to estuary/homebrew-flowctl that referenced this pull request Sep 19, 2024
## What's Changed
* Batch draft spec upserts, rather than attempting to paginate the response by @jshearer in estuary/flow#1629
* use max build_id for validating local specs by @psFried in estuary/flow#1636
* Update pagination to use 0-indexed inclusive ranges, and page by response length rather than fixed page size. by @jshearer in estuary/flow#1637
github-actions bot pushed a commit to estuary/homebrew-flowctl that referenced this pull request Sep 19, 2024
## What's Changed
* Batch draft spec upserts, rather than attempting to paginate the response by @jshearer in estuary/flow#1629
* use max build_id for validating local specs by @psFried in estuary/flow#1636
* Update pagination to use 0-indexed inclusive ranges, and page by response length rather than fixed page size. by @jshearer in estuary/flow#1637
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working change:unplanned This change is unplanned, useful for things like docs flowctl Issues related to the user facing CLI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants