[processing] fix handling for stdout and file outputs in GRASS #36618
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.
Description
Found this when working on another issue in Processing GRASS provider.
"Fake" (redirected from stdout) outputs in GRASS algorithms does not handled correctly if destination is temporary file. Algorithms just fail with Python error saying "File 'TEMPORARY_OUTPUT' does not exists". Normal file outputs works almost fine, except that in the log instead of valid output path we got also
TEMPORARY_OUTPUT
literal.Proposed PR fixes this by maintaining mapping between output name and destination path. This mapping then used to produce results map and also for converting text outputs into HTML.