api: Handle active cleanup from pull lock API #2144
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
victorges
commented
Apr 22, 2024
leszko
approved these changes
Apr 23, 2024
suhailkakar
added a commit
that referenced
this pull request
Apr 24, 2024
* Stick to the pull host while triggering the catalyst pull start (#2138) * Revert "Stick to the pull host while triggering the catalyst pull start (#2138)" (#2141) This reverts commit 29ad25a. * Stick to the pull host while triggering the catalyst pull start (#2142) * api: ingest: direct base & playback (#2139) * api: ingest: direct base & playback * fix * fix * implement for a specific hardcoded id for tests * fix * fix * api: Handle active cleanup from pull lock API (#2144) * refactor: improve api schema (#2109) * format yaml * add operationId to all endpoints * marked rooms api as deprecated * add tags to each endpoints * moved unused components to db-schema * add examples * override name for sdk generation * override operation name for sdk generatino * run prettier & fix typo * Update packages/api/src/schema/api-schema.yaml Co-authored-by: Victor Elias <[email protected]> * Update packages/api/src/schema/api-schema.yaml Co-authored-by: Victor Elias <[email protected]> * Update packages/api/src/schema/api-schema.yaml Co-authored-by: Victor Elias <[email protected]> * Update api-schema.yaml * fix: build error * revert: add new-asset-from-url-payload to api-schema.yaml * Update api-schema.yaml * fix build issue * hardcoded inputcreator filter * fix: create stream and loosening schema (#2134) * Update compile-schemas.js * fix: tsconfig * fix: revert additionalproperties * fix: remove InputCreatorId unknown * fix: api schema * fix: api schema * fix: revert changes to additional properties * fix: fixes from review * fix: lint --------- Co-authored-by: Victor Elias <[email protected]> Co-authored-by: Chase Adams <[email protected]> * api: Query isHealthy field as a string to handle JSOnull (#2143) * api: Query isHealthy field as a string to handle JSOnull * api: Add check on boolean fields filter value * api: moved objectStoreId and catalystPipelineStrategy to db schema (#2146) * api: moved params to db schema * Update db-schema.yaml * remove url * api: fix direct playback api (#2147) * fix june trigger (#2145) * fix sending track multiple times * add missing imports * replace track with page method --------- Co-authored-by: Rafał Leszko <[email protected]> Co-authored-by: gioelecerati <[email protected]> Co-authored-by: Victor Elias <[email protected]> Co-authored-by: Chase Adams <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this pull request do? Explain your changes. (required)
This is (yet another) hotfix for the active cleanup logic, specifically on the lock pull flow.
We were sometimes not allowing a stream to be locked because it was marked as active,
even tho it was lost (old lastSeen).
This adds some logic in the pull lock flow to handle the
lastSeenas well.Specific updates (required)
How did you test each of these updates (required)
yarn testDoes this pull request close any open issues?
Fixes isActive issue on lock pull
Checklist