Releases: mytardis/mydata
Releases · mytardis/mydata
v0.8.0
v0.8.0 RELEASE NOTES
The MyData v0.8.0 release is designed to coincide with the MyTardis v4.0 release and the
intention is to ensure compatibility with MyTardis 4.0 but avoid unexpected changes in
MyData for users familiar with v0.7.1. The v0.8.0 release includes only minimal bug fixes
relative to v0.7.1, plus the new User Group / Dataset folder structure included in v0.7.2-beta1.
CHANGES
1. Added support for a new User Group / Dataset folder structure (included in v0.7.2-beta1).
2. Fixed compatibility issue with MyTardis 4.0 (which uses newer django-tastypie for API).
3. Implemented a workaround for a difficult-to-reproduce counting problem where MyData
sometimes miscounts the number of DataFile lookups it has performed. The root cause
of the counting problem is still unknown, but the workaround ensures that MyData's
upload threads shut down cleanly, even if it over-counts the number of DataFile lookups.
4. Fixed Issue #129 - MyData changes permission of top-level staging directory to 660 when
DataFileObject URI is None.
5. Implemented a workaround for the "scheduled time is in the past" issue.
6. Fixed a bug which could cause MyData to log a 404 Client Error while monitoring upload progress.
v0.7.2
RELEASE NOTES
1. Added support for a new User Group / Dataset folder structure.
2. Fixed compatibility issue with the Django 1.11 MyTardis branch (which uses newer
django-tastypie).
3. Instead of allowing multiple SCP failures, MyData now stops its uploads after one failure
(if max retries has been exceeded for that upload), because we don't want MyData to
quickly create a large number of empty DataFile records due to "Disk quota exceeded"
errors.
4. Added the ability to ignore new datasets (via MyData.cfg not via the GUI yet), which is
useful when scanning a very large collection when you want to prioritize archiving older
datasets which may be ready for deletion from the machine MyData is running on.
5. Implemented a workaround for a difficult-to-reproduce counting problem where MyData
sometimes miscounts the number of DataFile lookups it has performed. The root cause
of the counting problem is still unknown, but the workaround ensures that MyData's
upload threads shut down cleanly, even if it over-counts the number of DataFile lookups.
6. Fixed Issue #129 - MyData changes permission of top-level staging directory to 660 when
DataFileObject URI is None.
7. Implemented a workaround for the "scheduled time is in the past" issue.
8. Setting isOwner to False in facility manager group ACLs created by MyData, to reduce
the clutter in the "Owned" section of MyTardis's "My Data" page.
v0.7.2-beta2
RELEASE NOTES
1. Added support for a new User Group / Dataset folder structure.
2. Fixed compatibility issue with the Django 1.11 MyTardis branch (which uses newer
django-tastypie).
3. Instead of allowing multiple SCP failures, MyData now stops its uploads after one failure
(if max retries has been exceeded for that upload), because we don't want MyData to
quickly create a large number of empty DataFile records due to "Disk quota exceeded"
errors.
4. Added the ability to ignore new datasets (via MyData.cfg not via the GUI yet), which is
useful when scanning a very large collection when you want to prioritize archiving older
datasets which may be ready for deletion from the machine MyData is running on.
5. Implemented a workaround for a difficult-to-reproduce counting problem where MyData
sometimes miscounts the number of DataFile lookups it has performed. The root cause
of the counting problem is still unknown, but the workaround ensures that MyData's
upload threads shut down cleanly, even if it over-counts the number of DataFile lookups.
6. Fixed Issue #129 - MyData changes permission of top-level staging directory to 660 when
DataFileObject URI is None.
7. Implemented a workaround for the "scheduled time is in the past" issue.
8. Setting isOwner to False in facility manager group ACLs created by MyData, to reduce
the clutter in the "Owned" section of MyTardis's "My Data" page.
v0.7.2-beta1
RELEASE NOTES
1. Added support for a new User Group / Dataset folder structure.
2. Fixed compatibility issue with the Django 1.11 LTS MyTardis branch (which uses newer
django-tastypie).
3. Instead of allowing multiple SCP failures, MyData now stops its uploads after one failure
(if max retries has been exceeded for that upload), because we don't want MyData to
quickly create a large number of empty DataFile records due to "Disk quota exceeded"
errors.
4. Added the ability to ignore new datasets (via MyData.cfg not via the GUI yet), which is
useful when scanning a very large collection when you want to prioritize archiving older
datasets which may be ready for deletion from the machine MyData is running on.
5. Implemented a workaround for a difficult-to-reproduce counting problem where MyData
sometimes miscounts the number of DataFile lookups it has performed. The root cause
of the counting problem is still unknown, but the workaround ensures that MyData's
upload threads shut down cleanly, even if it over-counts the number of DataFile lookups.
v0.7.1
RELEASE NOTES
1. Fixed issue with creating remote directories which could lead to incorrect permissions.
2. Connection timeout is now configurable in MyData.cfg; default increased from 5 to 10 seconds.
3. The legacy behaviour of minimizing to the System Tray on launch and when the user closes
the main window is now only used for the "Once", "Daily", "Weekly" and "Timer" schedule
types. For the "Manually", "On Startup" and "On Settings Saved" schedule types, the main
window is displayed on launch and attempting to close the window pops up a confirmation
dialog asking if the user wants to exit.
4. New --autoexit command-line argument can be used with "On Startup" schedule type.
5. Avoiding timer-triggered status bar update when the status is still "Looked up 0 of 0 files".
6. Fixed a bug where MyData loaded its settings twice, improving launch time.
7. Fixed a bug which could cause canceling scans and uploads to take longer than expected.
8. Some internal refactoring
9. When looking up datasets, MyData now matches the instrument ID (as well as the dataset description and experiment ID) if supported by the MyTardis API it is using.
v0.7.1-beta3
RELEASE NOTES
1. Fixed issue with creating remote directories which could lead to incorrect permissions.
2. Connection timeout is now configurable in MyData.cfg; default increased from 5 to 10 seconds.
3. The legacy behaviour of minimizing to the System Tray on launch and when the user closes
the main window is now only used for the "Once", "Daily", "Weekly" and "Timer" schedule
types. For the "Manually", "On Startup" and "On Settings Saved" schedule types, the main
window is displayed on launch and attempting to close the window pops up a confirmation
dialog asking if the user wants to exit.
4. New --autoexit command-line argument can be used with "On Startup" schedule type.
5. Avoiding timer-triggered status bar update when the status is still "Looked up 0 of 0 files".
6. Fixed a bug where MyData loaded its settings twice, improving launch time.
7. Fixed a bug which could cause canceling scans and uploads to take longer than expected.
8. Some internal refactoring
9. When looking up datasets, MyData now matches the instrument ID (as well as the dataset description and experiment ID) if supported by the MyTardis API it is using.
v0.7.1-beta2
RELEASE NOTES
1. Fixed issue with creating remote directories which could lead to incorrect permissions.
2. Connection timeout is now configurable in MyData.cfg; default increased from 5 to 10 seconds.
3. The legacy behaviour of minimizing to the System Tray on launch and when the user closes
the main window is now only used for the "Once", "Daily", "Weekly" and "Timer" schedule
types. For the "Manually", "On Startup" and "On Settings Saved" schedule types, the main
window is displayed on launch and attempting to close the window pops up a confirmation
dialog asking if the user wants to exit.
4. New --autoexit command-line argument can be used with "On Startup" schedule type.
5. Avoiding timer-triggered status bar update when the status is still "Looked up 0 of 0 files".
6. Fixed a bug where MyData loaded its settings twice, improving launch time.
7. Fixed a bug which could cause canceling scans and uploads to take longer than expected.
8. Some internal refactoring
v0.7.1-beta1
RELEASE NOTES
1. Fixed issue with creating remote directories which could lead to incorrect permissions.
2. Connection timeout is now configurable in MyData.cfg; default increased from 5 to 10 seconds.
3. The legacy behaviour of minimizing to the System Tray on launch and when the user closes
the main window is now only used for the "Once", "Daily", "Weekly" and "Timer" schedule
types. For the "Manually", "On Startup" and "On Settings Saved" schedule types, the main
window is displayed on launch and attempting to close the window pops up a confirmation
dialog asking if the user wants to exit.
4. New --autoexit command-line argument can be used with "On Startup" schedule type.
5. Avoiding timer-triggered status bar update when the status is still "Looked up 0 of 0 files".
6. Fixed a bug where MyData loaded its settings twice, improving launch time.
7. Fixed a bug which could cause canceling scans and uploads to take longer than expected.
8. Some internal refactoring
v0.7.0
RELEASE NOTES
MAJOR CHANGES
1.1 MyData now notifies the user if a new version is available.
1.2 Files found to be verified on MyTardis are now listed in a cache,
so subsequent lookups are fast.
1.3 Removed file chunking, improving upload speed, but partial uploads
can no longer be resumed.
1.4 On Windows, settings are now saved to a central location (C:\ProgramData)
accessible to all users.
1.5 Added initial support for uploading files at the experiment level,
not within any dataset folder.
1.6 Significantly improved test coverage.
MINOR CHANGES
2.1 Some new configurable settings (including immutable_datasets) can be specified in MyData.cfg:
http://mydata.readthedocs.io/en/latest/settings.html#settings-only-configurable-in-mydata-cfg
2.2 MD5 sums can now be faked (by settings fake_md5_sum = True in MyData.cfg).
There is no functionality yet to POST corrected MD5 sums. But faking MD5
sums can help to isolate performance bottlenecks.
2.3 MyData debug log path can now be specified as an environment variable
(MYDATA_DEBUG_LOG_PATH), which is used for making debug logs available
from continuous integration builds.
2.4 Using a standard status bar instead of buggy EnhancedStatusBar
2.5 Fixed an issue where MyData complained if there was a folder other than "MyTardis" at the same level as the "MyTardis" folder in the Username/"MyTardis"/Experiment/Dataset folder structure.
2.6 On Windows, upgraded SCP binaries are now provided for both 32-bit and 64-bit.
2.7 MyData now measures and displays upload speeds
IMPROVED LINUX COMPATIBILITY
4.1 MyData on Linux now uses errand_boy which is more efficient than
subprocess, due to subprocess's use of os.fork.
4.2 Fixed Linux bug which could cause MyData to freeze when exiting.
4.3. Removed -oIdentiesOnly which doesn't play nicely with some Linux
OpenSSH environments (e.g. RHEL7 with gnome-key-ring).
4.4 Fixed settings dialog spacing on RHEL7 (GNOME classic).
4.5 When running on Ubuntu Unity, MyData checks that the indicator-systemtray-unity
is installed and displays an error if it isn't.
v0.7.0-beta17
RELEASE NOTES
MAJOR CHANGES
1.1 MyData now notifies the user if a new version is available.
1.2 Files found to be verified on MyTardis are now listed in a cache,
so subsequent lookups are fast.
1.3 Removed file chunking, improving upload speed, but partial uploads
can no longer be resumed.
1.4 On Windows, settings are now saved to a central location (C:\ProgramData)
accessible to all users.
1.5 Added initial support for uploading files at the experiment level,
not within any dataset folder.
1.6 Significantly improved test coverage.
MINOR CHANGES
2.1 Some new configurable settings (including immutable_datasets) can be specified in MyData.cfg:
http://mydata.readthedocs.io/en/latest/settings.html#settings-only-configurable-in-mydata-cfg
2.2 MD5 sums can now be faked (by settings fake_md5_sum = True in MyData.cfg).
There is no functionality yet to POST corrected MD5 sums. But faking MD5
sums can help to isolate performance bottlenecks.
2.3 MyData debug log path can now be specified as an environment variable
(MYDATA_DEBUG_LOG_PATH), which is used for making debug logs available
from continuous integration builds.
2.4 Using a standard status bar instead of buggy EnhancedStatusBar
2.5 Fixed an issue where MyData complained if there was a folder other than "MyTardis" at the same level as the "MyTardis" folder in the Username/"MyTardis"/Experiment/Dataset folder structure.
2.6 On Windows, upgraded SCP binaries are now provided for both 32-bit and 64-bit.
2.7 MyData now measures and displays upload speeds
IMPROVED LINUX COMPATIBILITY
4.1 MyData on Linux now uses errand_boy which is more efficient than
subprocess, due to subprocess's use of os.fork.
4.2 Fixed Linux bug which could cause MyData to freeze when exiting.
4.3. Removed -oIdentiesOnly which doesn't play nicely with some Linux
OpenSSH environments (e.g. RHEL7 with gnome-key-ring).
4.4 Fixed settings dialog spacing on RHEL7 (GNOME classic).
4.5 When running on Ubuntu Unity, MyData checks that the indicator-systemtray-unity
is installed and displays an error if it isn't.