Skip to content

[PR] fix(dataproc): only create output artifacts for the selected output mode - #136

Merged
Kaszanas merged 1 commit into
devfrom
135-fix-all-replays-json-always-created
Sep 8, 2026
Merged

[PR] fix(dataproc): only create output artifacts for the selected output mode#136
Kaszanas merged 1 commit into
devfrom
135-fix-all-replays-json-always-created

Conversation

@Kaszanas

@Kaszanas Kaszanas commented Sep 8, 2026

Copy link
Copy Markdown
Owner

all_replays.json, package_N.zip, and package_summary_N.json were each being created unconditionally, regardless of whether -single_json_output or zip packaging was actually selected. Gate the single-JSON writer goroutine on cliFlags.SingleJsonOutput, and gate zip-writer init/save/finalize on a new writeZipPackage flag
(packageToZipBool && !cliFlags.SingleJsonOutput), so only the artifacts for the chosen mode get written.

Also add SetDefaultLogging(), a basic stdout logger active before SetLogging can run (i.e. while flags are still being parsed), so failures during flag parsing are visible instead of relying on logrus's uninitialized zero-value default.

all_replays.json, package_N.zip, and package_summary_N.json were each
being created unconditionally, regardless of whether -single_json_output
or zip packaging was actually selected. Gate the single-JSON writer
goroutine on cliFlags.SingleJsonOutput, and gate zip-writer
init/save/finalize on a new writeZipPackage flag
(packageToZipBool && !cliFlags.SingleJsonOutput), so only the artifacts
for the chosen mode get written.

Also add SetDefaultLogging(), a basic stdout logger active before
SetLogging can run (i.e. while flags are still being parsed), so
failures during flag parsing are visible instead of relying on logrus's
uninitialized zero-value default.
@Kaszanas Kaszanas added this to the 2.2.0 milestone Sep 8, 2026
@Kaszanas Kaszanas self-assigned this Sep 8, 2026
@Kaszanas Kaszanas linked an issue Sep 8, 2026 that may be closed by this pull request
@Kaszanas
Kaszanas merged commit 113ae35 into dev Sep 8, 2026
5 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 8, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

All Replays JSON is always created

1 participant