Releases: mytardis/mydata
Releases · mytardis/mydata
v0.6.1
RELEASE NOTES
- Various performance improvements affecting:
- UI responsiveness
- CPU usage
- memory footprint
- upload speed
- MyData can now begin uploads as soon as the first folder has been
scanned, instead of having to wait for all folders to be scanned.
- Fixed a bug where MyData couldn't upload zero-sized files.
- Fixed bug where Settings dialog displayed the excludes file path in the includes file field.
- On Windows, we now build a console binary for MyData as well as the GUI
binary. If an unhandled exception is suspected, it can be difficult
to debug in a GUI application, because there is no STDERR pipe.
The console version of MyData is called MyData.com (compared with
MyData.exe for the GUI application), meaning that if MyData is run
from the command-line (without specifying the .com or .exe extension),
the console version will be run, but the installed shortcuts will point
to the GUI version.
v0.6.1-beta4
RELEASE NOTES
- Various performance improvements affecting:
- UI responsiveness
- CPU usage
- memory footprint
- upload speed
- MyData can now begin uploads as soon as the first folder has been
scanned, instead of having to wait for all folders to be scanned.
- Fixed a bug where MyData couldn't upload zero-sized files.
- Fixed bug where Settings dialog displayed the excludes file path in the includes file field.
- On Windows, we now build a console binary for MyData as well as the GUI
binary. If an unhandled exception is suspected, it can be difficult
to debug in a GUI application, because there is no STDERR pipe.
The console version of MyData is called MyData.com (compared with
MyData.exe for the GUI application), meaning that if MyData is run
from the command-line (without specifying the .com or .exe extension),
the console version will be run, but the installed shortcuts will point
to the GUI version.
v0.6.1-beta3
Merge pull request #72 from mytardis/develop Merging more into master for v0.6.1-beta3 build
v0.6.1-beta2
Merge pull request #70 from mytardis/develop Merging into master for v0.6.1-beta2 build
v0.5.6p1
RELEASE NOTES
- On Windows, we now build a console binary for MyData as well as the GUI
binary. If an unhandled exception is suspected, it can be difficult
to debug in a GUI application, because there is no STDERR pipe.
The console version of MyData is called MyData.com (compared with
MyData.exe for the GUI application), meaning that if MyData is run
from the command-line (without specifying the .com or .exe extension),
the console version will be run, but the installed shortcuts will point
to the GUI version.
v0.6.1-beta1
RELEASE NOTES
- On Windows, we now build a console binary for MyData as well as the GUI
binary. If an unhandled exception is suspected, it can be difficult
to debug in a GUI application, because there is no STDERR pipe.
The console version of MyData is called MyData.com (compared with
MyData.exe for the GUI application), meaning that if MyData is run
from the command-line (without specifying the .com or .exe extension),
the console version will be run, but the installed shortcuts will point
to the GUI version.
v0.6.0
RELEASE NOTES
1. New Functionality
- Test runs ("dry runs").
- New "User Group / Experiment / Dataset" folder structure.
- Support for includes / excludes (file pattern matching).
- Upload invalid user folders checkbox now also works for user groups.
2. Changes in Appearance
- New Test Run toolbar icon.
- Refresh toolbar icon has been replaced with an Upload toolbar icon.
The functionality is still the same (scan / re-scan folders and
upload if not already uploaded).
- Changed field order in Settings Dialog's filtering panel to User, Experiment, Dataset.
3. Improved Functionality
- More efficient data folder scanning (previously, os.walk was being called twice,
once to count files, and once to list them).
- More responsive to Stop requests: Settings validation now checks periodically
for ShouldAbort().
- MyTardis URL testing during settings validation now uses the MyTardis site's API URL,
instead of its About page, whose response time gives a more realistic indication of
whether MyData will be able to perform adequately.
- GUI responsiveness is improved by disabling debug-level logging by default. It can be
enabled using a new "Debug logging" checkbox in the Log view.
4. Bug Fixes
- If the user pressed Cancel from the Settings dialog after a failed settings validation,
the settings were not saved to disk, but they were saved in memory. Now they are
rolled back when Cancel is pressed.
- Ensure that attempts to load settings from server can't raise a critical exception.
- Ensure that a "(Tentative)" IP address annotation isn't included in the local IP address
POSTed to the MyTardis API.
- For approved uploads via staging, ensure that the correct storage box can be reliably
determined from the POSTed data. (There is a related change in the
https://github.com/mytardis/mytardis-app-mydata server-side app).
- Fixed "start automatically on login" functionality on Linux.
v0.6.0-beta11
RELEASE NOTES
1. New Functionality
- Test runs ("dry runs").
- New "User Group / Experiment / Dataset" folder structure.
- Support for includes / excludes (file pattern matching).
- Upload invalid user folders checkbox now also works for user groups.
2. Changes in Appearance
- New Test Run toolbar icon.
- Refresh toolbar icon has been replaced with an Upload toolbar icon.
The functionality is still the same (scan / re-scan folders and
upload if not already uploaded).
- Changed field order in Settings Dialog's filtering panel to User, Experiment, Dataset.
3. Improved Functionality
- More efficient data folder scanning (previously, os.walk was being called twice,
once to count files, and once to list them).
- More responsive to Stop requests: Settings validation now checks periodically
for ShouldAbort().
- MyTardis URL testing during settings validation now uses the MyTardis site's API URL,
instead of its About page, whose response time gives a more realistic indication of
whether MyData will be able to perform adequately.
- GUI responsiveness is improved by disabling debug-level logging by default. It can be
enabled using a new "Debug logging" checkbox in the Log view.
4. Bug Fixes
- If the user pressed Cancel from the Settings dialog after a failed settings validation,
the settings were not saved to disk, but they were saved in memory. Now they are
rolled back when Cancel is pressed.
- Ensure that attempts to load settings from server can't raise a critical exception.
- Ensure that a "(Tentative)" IP address annotation isn't included in the local IP address
POSTed to the MyTardis API.
- For approved uploads via staging, ensure that the correct storage box can be reliably
determined from the POSTed data. (There is a related change in the
https://github.com/mytardis/mytardis-app-mydata server-side app).
- Fixed "start automatically on login" functionality on Linux.
v0.6.0-beta10
RELEASE NOTES
1. New Functionality
- Test runs ("dry runs").
- New "User Group / Experiment / Dataset" folder structure.
- Support for includes / excludes (file pattern matching).
- Upload invalid user folders checkbox now also works for user groups.
2. Changes in Appearance
- New Test Run toolbar icon.
- Refresh toolbar icon has been replaced with an Upload toolbar icon.
The functionality is still the same (scan / re-scan folders and
upload if not already uploaded).
- Changed field order in Settings Dialog's filtering panel to User, Experiment, Dataset.
3. Improved Functionality
- More efficient data folder scanning (previously, os.walk was being called twice,
once to count files, and once to list them).
- More responsive to Stop requests: Settings validation now checks periodically
for ShouldAbort().
- MyTardis URL testing during settings validation now uses the MyTardis site's API URL,
instead of its About page, whose response time gives a more realistic indication of
whether MyData will be able to perform adequately.
- GUI responsiveness is improved by disabling debug-level logging by default. It can be
enabled using a new "Debug logging" checkbox in the Log view.
4. Bug Fixes
- If the user pressed Cancel from the Settings dialog after a failed settings validation,
the settings were not saved to disk, but they were saved in memory. Now they are
rolled back when Cancel is pressed.
- Ensure that attempts to load settings from server can't raise a critical exception.
- Ensure that a "(Tentative)" IP address annotation isn't included in the local IP address
POSTed to the MyTardis API.
- For approved uploads via staging, ensure that the correct storage box can be reliably
determined from the POSTed data. (There is a related change in the
https://github.com/mytardis/mytardis-app-mydata server-side app).
- Fixed "start automatically on login" functionality on Linux.
v0.6.0-beta9
RELEASE NOTES
1. New Functionality
- Test runs ("dry runs").
- New "User Group / Experiment / Dataset" folder structure.
- Support for includes / excludes (file pattern matching).
- Upload invalid user folders checkbox now also works for user groups.
2. Changes in Appearance
- New Test Run toolbar icon.
- Refresh toolbar icon has been replaced with an Upload toolbar icon.
The functionality is still the same (scan / re-scan folders and
upload if not already uploaded).
- Changed field order in Settings Dialog's filtering panel to User, Experiment, Dataset.
3. Improved Functionality
- More efficient data folder scanning (previously, os.walk was being called twice,
once to count files, and once to list them).
- More responsive to Stop requests: Settings validation now checks periodically
for ShouldAbort().
- MyTardis URL testing during settings validation now uses the MyTardis site's API URL,
instead of its About page, whose response time gives a more realistic indication of
whether MyData will be able to perform adequately.
4. Bug Fixes
- If the user pressed Cancel from the Settings dialog after a failed settings validation,
the settings were not saved to disk, but they were saved in memory. Now they are
rolled back when Cancel is pressed.
- Ensure that attempts to load settings from server can't raise a critical exception.
- Ensure that a "(Tentative)" IP address annotation isn't included in the local IP address
POSTed to the MyTardis API.
- For approved uploads via staging, ensure that the correct storage box can be reliably
determined from the POSTed data. (There is a related change in the
https://github.com/mytardis/mytardis-app-mydata server-side app).