Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[processing] fix handling for stdout and file outputs in GRASS #36618

Merged
merged 2 commits into from May 24, 2020
Merged

[processing] fix handling for stdout and file outputs in GRASS #36618

merged 2 commits into from May 24, 2020

Conversation

alexbruy
Copy link
Contributor

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.

@alexbruy alexbruy added Processing Relating to QGIS Processing framework or individual Processing algorithms Bug Either a bug report, or a bug fix. Let's hope for the latter! backport release-3_10 labels May 21, 2020
@alexbruy alexbruy requested a review from nyalldawson May 21, 2020 09:56
@alexbruy
Copy link
Contributor Author

@nyalldawson may I ask you to take a look?

@nyalldawson
Copy link
Collaborator

I've got to admit, I don't fully understand the logic here (the original logic & the new logic 😄 )!

But I do know that since 3.0 there's been a number of disabled grass tests which relied on html outputs. I wonder if these relate to the same underlying cause and could now be re-enabled?

@alexbruy
Copy link
Contributor Author

Probably I have missed when we disabled some GRASS tests but there are some broken algs and I'm about to submit another PR which fixes them and adds tests. Will check if there are any disabled tests and try to re-enable them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Processing Relating to QGIS Processing framework or individual Processing algorithms
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants