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
The following issue was observed with the current develop branch (date of trial 02.09.2022), using the rdms-test server.
The behavior of the buttons in the "Dialog" window that is opened when files are uploaded via the "Up and Download" tab of iBridges should be investigated.
For Upload, the window looks:
If the "Upload" button is pressed. The whole program crashed with the following message:
QThread: Destroyed while thread is still running
fish: “./irods-iBridgesGui.py” terminated by signal SIGABRT (Abort)
The same happens when the "Cancel" button is pressed (remark: the fish part results from my usage of fish shell, please do not be confused by this)
This was not just observed for the download of files, but similar also when uploading.
In my opinion, the following behavior would be good:
When a transfer is ongoing, the "Upload" or "Download" button should be blocked and not clickable.
Pressing the "Cancel" button should not result in the whole iBridges client crashing. Instead, it should bring one back to the "Up and Download" tab. It should be also taken care of what happens if the "Cancel" button is hit while a transfer is ongoing. It should not result in corrupt/not correctly transferred files. In my case, it resulted in two files that are marked as locked and which cannot be deleted using the delete function of iBridges:
Output of the command line also shows both files in a locked stage:
The following issue was observed with the current develop branch (date of trial 02.09.2022), using the rdms-test server.
The behavior of the buttons in the "Dialog" window that is opened when files are uploaded via the "Up and Download" tab of iBridges should be investigated.
For Upload, the window looks:
If the "Upload" button is pressed. The whole program crashed with the following message:
The same happens when the "Cancel" button is pressed (remark: the
fish
part results from my usage of fish shell, please do not be confused by this)This was not just observed for the download of files, but similar also when uploading.
In my opinion, the following behavior would be good:
Output of the command line also shows both files in a locked stage:
The text was updated successfully, but these errors were encountered: