Skip to content

Fix async error output and release verifier syntax#1263

Draft
cursor[bot] wants to merge 3 commits into
rc-v0.6.7from
cursor/critical-correctness-bugs-5fb9
Draft

Fix async error output and release verifier syntax#1263
cursor[bot] wants to merge 3 commits into
rc-v0.6.7from
cursor/critical-correctness-bugs-5fb9

Conversation

@cursor

@cursor cursor Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Fixes two high-severity correctness defects found while reviewing recent release-window changes.

Fixes

  • Async API processing now writes terminal error artifacts for source API failures and async redirect failures, so clients that received 202 Accepted do not poll an empty output location indefinitely.
  • Release bundle verification helper now parses correctly; the stray } prevented tools/release/verify-bundles.sh from running at all.

Features

Logistics

Change implications

  • dependencies added/changed? no
  • something important to note in future release notes?
    • Async output destinations now receive an error artifact with Error and Psoxy-Version metadata when source/redirect processing fails.
    • No Terraform plan/apply impact.
    • No breaking changes.

Validation performed:

  • bash -n tools/release/lib/verify-bundles-lib.sh && bash -n tools/release/verify-bundles.sh && ./tools/release/verify-bundles.sh --help
  • mvn -pl core -am -Dtest=ApiDataRequestHandlerTest -Dsurefire.failIfNoSpecifiedTests=false test
  • mvn -pl core -am test
Open in Web View Automation 

cursoragent and others added 3 commits June 5, 2026 11:21
Co-authored-by: Erik Schultink <eschultink@users.noreply.github.com>
Co-authored-by: Erik Schultink <eschultink@users.noreply.github.com>
Co-authored-by: Erik Schultink <eschultink@users.noreply.github.com>
@eschultink eschultink changed the base branch from main to rc-v0.6.3 June 8, 2026 16:51
Base automatically changed from rc-v0.6.3 to main June 8, 2026 17:34
An error occurred while trying to automatically change base from rc-v0.6.3 to main June 8, 2026 17:34
@eschultink eschultink changed the base branch from main to rc-v0.6.4 June 8, 2026 20:24
Base automatically changed from rc-v0.6.4 to main June 11, 2026 17:37
@eschultink eschultink changed the base branch from main to rc-v0.6.5 June 11, 2026 20:53
ProcessingContext processingContext) throws IOException {
if (!processingContext.getAsync()) {
return response;
}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

very unuseful encapsulation, imho.

return response;
}

private void writeAsyncErrorContent(ProcessedContent content, String errorCause,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

split of this and method above seems like poor code style; just unnecessary complexity.

builder.body("Error communicating with source API: " + e.getMessage());
log.log(Level.SEVERE, "Error communicating with source API", e);
return builder.build();
return writeAsyncErrorResponseIfNeeded(builder.build(), processingContext);

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

seems weird to call build() here - not just pass the builder ...

Base automatically changed from rc-v0.6.5 to main June 17, 2026 16:19
@eschultink eschultink changed the base branch from main to rc-v0.6.6 June 17, 2026 16:30
Base automatically changed from rc-v0.6.6 to main June 18, 2026 20:25
@eschultink eschultink changed the base branch from main to rc-v0.6.7 June 18, 2026 20:34
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.

2 participants