[FEAT] Enhance map creation functions with verbose debugging option - #287
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
treee111
force-pushed
the
Verbose-Osmosis-on-Windows
branch
from
August 20, 2026 13:32
bf6e01b to
7044490
Compare
…tforms Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
treee111
approved these changes
Aug 20, 2026
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
2 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.
This PR…
Displays debug screen output for the two Osmosis processes under Windows when the "Output debugger logger messages" option is selected.
Considerations and implementations
Why? In the current version when an error occurs on Windows in Osmosis (batch file) the program just hangs with no feedback what so ever to the user who can only wait endlessly and doesn't get any clue to the underlying issue. Which most of the time is a Java out of heap space error.
Fixes issue: #285
How to test
Pull Request Checklist