Skip to content

Fix output strategy handling in NetworkClient client-side runs - #1

Open
bohdansolovie wants to merge 5 commits into
developfrom
fix/network-client-output-strategy
Open

Fix output strategy handling in NetworkClient client-side runs#1
bohdansolovie wants to merge 5 commits into
developfrom
fix/network-client-output-strategy

Conversation

@bohdansolovie

@bohdansolovie bohdansolovie commented Jan 28, 2026

Copy link
Copy Markdown
Owner

Fixes TODO comments by implementing proper output strategy handling for client-side process execution in NetworkClient.

Changes:

  • Replace None outputStrategy with BufferedOutput(log) for both JVM and native runs
  • Buffers output until completion, then logs through console interface
  • Prevents output interleaving with NetworkClient's synchronized output handling
  • Ensures consistent logging behavior

Why BufferedOutput?
The TODO explicitly requested "buffered output" handling. BufferedOutput:

  • Matches the TODO requirement
  • Prevents interleaving issues
  • Provides controlled, consistent output through the logger

eed3si9n and others added 5 commits January 28, 2026 02:27
**Problem**
Strings are used to pass paths around.

**Solution**
This cleans up the Scala instance construction code.
…rtiesFor (sbt#8641)

**Problem**
getPropertiesFor method calls getResource().openStream() without checking
if getResource returns null. When a resource doesn't exist, this causes
a NullPointerException with no context about which resource was missing.

**Solution**
Added null check before calling openStream() and throw a descriptive
FileNotFoundException with the resource name if the resource is not found.
This prevents NullPointerException and provides better error messages.

Generated-by: Auto
)

When a bundle upload to Central Portal fails, the error now displays the HTTP response body instead of just the status code. This provides more useful debugging information, as the response body typically contains detailed error messages from the server.
Fixes sbt#8627

- Use ${OUT} placeholder and remove StringVirtualFile1 special-case handling
- Make dirZipExt check generic (use vf instead of svf: StringVirtualFile1)
- Let syncBlobs handle StringVirtualFile1 transparently via fileConverter.toPath()
Replace TODO comments with BufferedOutput strategy for client-side
process execution. This prevents output interleaving and ensures
consistent logging through the NetworkClient's logger.

- Use BufferedOutput(log) for both JVM and native runs
- Buffers output until completion, then logs through console interface
- Prevents interleaving with NetworkClient's synchronized output handling

Generated-by: Gen-AI tools
@bohdansolovie
bohdansolovie force-pushed the fix/network-client-output-strategy branch from 26707d0 to c48d387 Compare January 28, 2026 23:32
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.

4 participants