enable github actions on roblutt/windows-ci #47
Closed
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
Signed-off-by: Josh Usiskin <[email protected]>
Signed-off-by: Josh Usiskin <[email protected]>
…D/VIRTUAL
BREAKING CHANGES:
The changes here are a result of breaking changes in the deadline-cloud library.
- AssetLoadingMethod class is renamed to JobAttachmentsFileSystem
- PRELOAD, ON_DEMAND enum string values for AssetLoadingMethod are now called COPIED, VIRTUAL
Signed-off-by: Phanindra Bhagavatula <[email protected]>
Signed-off-by: Charles Moore <[email protected]>
Signed-off-by: Charles Moore <[email protected]>
Signed-off-by: Jericho Tolentino <[email protected]>
- `BatchGetJobEntity` API response data validation - `ConfigFile` model validation (pydantic) - `Capabilities` model validation (pydantic) Signed-off-by: Gahyun Suh <[email protected]>
Signed-off-by: Charles Moore <[email protected]>
Signed-off-by: Jericho Tolentino <[email protected]>
When calling a deadline cloud service API and getting a throttle/retry response the exception object may contain a "retryAfterSeconds" field alongside the error. When that field is present, the calling client should treat that as a request to retry in no sooner than the given number of seconds; it is a load-shedding mechanism for the service. We should respect the service's request. Solution: Added to the logic of all of the deadline-cloud API wrappers to have them extract the value of the "retryAfterSeconds" field if it's present, and pass that to our backoff-delay calculator. We use the value as a lower limit on the returned delay. I also made the scheduler use the API wrapper for update_worker; it still had its own implementation that didn't properly handle exceptions. This necessitated adding the ability to interrupt the update_worker's throttled-retries so preserve the functionality at that call site. Signed-off-by: Daniel Neilson <[email protected]>
Signed-off-by: Jericho Tolentino <[email protected]>
roblutt
force-pushed
the
roblutt/windev
branch
2 times, most recently
from
33c9c44 to
c81b35b
Compare
Signed-off-by: Gahyun Suh <[email protected]>
roblutt
force-pushed
the
roblutt/windev
branch
4 times, most recently
from
67fe9ed to
d898506
Compare
Signed-off-by: Robert Luttrell <[email protected]>
roblutt
force-pushed
the
roblutt/windev
branch
from
d898506 to
d41d035
Compare
jusiskin
added a commit
to jusiskin/deadline-cloud-worker-agent
that referenced
this pull request
Sep 4, 2024
…eadline#47) Signed-off-by: Josh Usiskin <[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.
test