Bug report #20051
SAGA "Fill Sink" keeps running
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Processing/SAGA | ||
| Affected QGIS version: | 3.2.3 | Regression?: | Yes |
| Operating System: | Windows 7 | Easy fix?: | No |
| Pull Request or Patch supplied: | No | Resolution: | not reproducable |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 27873 |
Description
Using SAGA Fill Sink ans Fill Sink (Wang & Liu)I´m only presented to save in SDAT filformat.
In 2.18 there are multiple raster data formats.
I can type in .tif
If I click 'Open output after running algorithm' The process keep running and I have to close the program.
Associated revisions
[processing][SAGA] Resync Fill Sinks descriptions, add tests
Refs #20051
[processing][SAGA] Resync Fill Sinks descriptions, add tests
Refs #20051
(cherry picked from commit efd54f862f9319abb47149a445c2370e7e9170d8)
History
#1
Updated by Lene Fischer about 6 years ago
The process keeps runnning - but the data is processed and is placed in C:\Users\dlt265\AppData\Local\Temp
#2
Updated by Nyall Dawson about 6 years ago
In 3.0 the choice was made to only expose the native output formats from 3rd party providers like saga. We did this to avoid silently changing the outputs during conversion to non native formats, e.g. possibly changing field types and data types which aren't a direct match for the original output.
Better to only allow the actual supported formats and require users to convert the outputs themselves, making any format specific compatibility issues their responsibility.
#3
Updated by Giovanni Manghi about 6 years ago
- Status changed from Open to Feedback
- Crashes QGIS or corrupts data changed from Yes to No
- Subject changed from SAGA Fill Sink save in SDAT fil and Open output - keep running to SAGA "Fill Sink" keeps running
Lene Fischer wrote:
The process keeps runnning - but the data is processed and is placed in C:\Users\dlt265\AppData\Local\Temp
I cannot confirm here on master/linux with data of my own. Can you attach sample data that in your case causes the tool to keep running?
Also why tagging this a regression? did it worked normally in a previous release?
#4
Updated by Paolo Cavallini almost 6 years ago
Please give feedback or close this issue.
#5
Updated by Nyall Dawson almost 6 years ago
- Status changed from Feedback to Closed
- Resolution set to not reproducable
I can't reproduce, and there's now unit tests covering this. I think it's safe to close.