Repository navigation
feat: sync Java client with Apify OpenAPI spec v2-2026-10-08T073338Z - #21
Merged
Merged
Conversation
…c v2-2026-10-08T073338Z - UserProfile.getReadme() (new Profile.readme spec field) - waitForResources on Actor/Task start+call options: retries a run start rejected for lack of memory or a concurrent-run slot, mirroring apify-client-js#1091 - waitForFinish now gives up on a run/build id that keeps 404-ing after 3s instead of polling it for the whole wait budget, mirroring apify-client-js#1124 - StreamedLog reopens a log stream that ended with zero bytes (a run that hasn't logged anything yet) instead of silently giving up, with a one-shot fallback fetch on stop(), mirroring apify-client-js#1105
…en update - README: fix a stray old Version.API_SPEC_VERSION mention left over from the version bump - StreamedLog.stop()/close(): restore the reference client's ~1s grace window before force-closing the live stream, so a message already in flight (e.g. the run's last line) is not cut off - the earlier immediate-close only unblocked an already-blocked read, it did not give a pending one a chance to arrive - StreamedLog: fix a stop()/close() vs. reader-thread deadlock risk (both are `synchronized` methods that may block in `join()` while holding the monitor a `synchronized` activeStream publish from the reader thread would then need) by publishing the reopened stream as a plain volatile write instead, and explicitly close it too if a stop raced in while it was in flight - ResourceContext.waitForFinish: tolerate a 200 response with a null `data` body as "not yet available" again (it stopped doing so when the 404-bound fix swapped in a stricter accessor), instead of a NullPointerException - RunStartSupport: clamp waitForResourcesSecs before computing its deadline, so a value near Long.MAX_VALUE cannot overflow it
It described the field as "the instant it was last seen present", but it is set to the instant the resource was first observed absent.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
Syncs the Java client from OpenAPI spec
v2-2026-10-01T153946Ztov2-2026-10-08T073338Z(apify/apify-docs#3043, #3044, #3042) and ports the Java-relevant changes from the referenceapify-client-jsbatch (apify/apify-client-js#1091, #1122, #1121, #1123, #1124, #1107, #1137, #1105).UserProfile.getReadme()for the spec's newProfile.readmefield (apify-docs#3043).waitForResourcesonActorStartOptions/TaskStartOptionsand the matchingActorCallOptions/TaskCallOptions: retries a run start rejected for lack of memory or a concurrent-run slot (apify-client-js#1091). Implemented ininternal/RunStartSupport.RunClient.waitForFinish()/BuildClient.waitForFinish()now throwNotFoundErroronce a run/build has answered 404 for 3s straight, instead of polling for the whole wait budget (apify-client-js#1124).StreamedLogreopens a live log stream that ends with zero bytes (a run that hasn't logged yet) with capped backoff, and does a one-shot fetch if stopped before any content arrived (apify-client-js#1105); keeps the reference client's ~1s stop grace window (apify-client-js#1123).No Java change was needed for apify-client-js#1107 (generated-model renames), #1121 (
unwindalready a string list), #1122 (restartOnErrornot exposed at top level) or #1137 (docs), nor for apify-docs#3044 (schema renames, no wire change) and #3042 (useCachedefault, documentation only).Version bumped to
0.8.0;CHANGELOG.md,README.mdanddocs/*.mdupdated.