You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.
Using GUI to run through Use Case 6 happy path. Applied a subset_temporal operation.
In the “New Operation Step” window, selected a start time of 2007-01-01
Then cleared the end time field. Expected the start time which had just been entered not to change.
Actual behavior
The start time reset itself to 1980-01-01.
Notes:
Similar behaviour is seen if the end time has been entered and then the start time is cleared. The end time will reset itself to the current date.
Similar behaviour is seen in “Edit Operation Step” window as well as “New Operation Step” window
Similar behaviour is seen for other operations which contain a time range: anomaly_internal and open_dataset
Steps to reproduce the problem
Ensure there is at least one resource of type Dataset in the workspace
From operations panel, select subset_temporal then Apply
In New Operation Step window, select a Dataset resource
Next to TimeRange, enter a start time (the end time field is then automatically populated with today’s date)
Clear the end time field and see that the start time has been reset to 1980-01-01
Enter new end time
Clear start time. Now end time has been reset.
Specifications
Cate 0.9.0-dev.5
Windows 7 Professional
The text was updated successfully, but these errors were encountered:
Expected behavior
Using GUI to run through Use Case 6 happy path. Applied a subset_temporal operation.
In the “New Operation Step” window, selected a start time of 2007-01-01
Then cleared the end time field. Expected the start time which had just been entered not to change.
Actual behavior
The start time reset itself to 1980-01-01.
Notes:
Steps to reproduce the problem
Specifications
Cate 0.9.0-dev.5
Windows 7 Professional
The text was updated successfully, but these errors were encountered: