auto-tx issueshttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues2022-10-20T11:44:20Zhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/85Human-readable sizes should include at least one digit after the dot2022-10-20T11:44:20ZNiko EhrenfeuchterHuman-readable sizes should include at least one digit after the dotIt doesn't make much of a difference whether it's `33.4 GB` or `33.8 GB` but e.g. everything between `1 TB` and `2 TB` will currently be rounded and presented as `1 TB` - which is not very practical...It doesn't make much of a difference whether it's `33.4 GB` or `33.8 GB` but e.g. everything between `1 TB` and `2 TB` will currently be rounded and presented as `1 TB` - which is not very practical...VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/84Startup-log doesn't contain timestamps2022-10-20T11:39:22ZNiko EhrenfeuchterStartup-log doesn't contain timestampsThat makes it impossible to understand *when* an error has happened...That makes it impossible to understand *when* an error has happened...VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/83Periodically re-check on new transfers put on hold for permission issues2022-10-20T11:24:46ZNiko EhrenfeuchterPeriodically re-check on new transfers put on hold for permission issuesIf a user adds a new transfer that cannot be moved to the *processing* location AutoTx will ignore the whole user's `INCOMING` folder for the service **session** (meaning until the service gets restarted).
Instead of blocking the whole ...If a user adds a new transfer that cannot be moved to the *processing* location AutoTx will ignore the whole user's `INCOMING` folder for the service **session** (meaning until the service gets restarted).
Instead of blocking the whole folder it would be much more user-friendly to periodically re-check (say, every 5 minutes) if the new files can be moved now.https://git.scicore.unibas.ch/vamp/auto-tx/-/issues/82Submitting folders with only 3 letter names fails2021-11-25T11:19:53ZNiko EhrenfeuchterSubmitting folders with only 3 letter names failsUsing the tray app to submit a folder with a 3-letter-name (the reported one was "bud") fails with the error message saying "submitting entire drives" is not possible.
Looks like a bug in the corresponding check as renaming the folder w...Using the tray app to submit a folder with a 3-letter-name (the reported one was "bud") fails with the error message saying "submitting entire drives" is not possible.
Looks like a bug in the corresponding check as renaming the folder with a longer name was a quick workaround.VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/81Report status in tray app when service is suspended / in exponential backoff2021-07-19T10:52:56ZNiko EhrenfeuchterReport status in tray app when service is suspended / in exponential backoffIf a user attempts to initiate a new transfer when the service is in exponential backoff the tray app doesn't report this status correctly - making the user believe their transfer has been processed correctly whereas nothing is appearing...If a user attempts to initiate a new transfer when the service is in exponential backoff the tray app doesn't report this status correctly - making the user believe their transfer has been processed correctly whereas nothing is appearing in the target location.VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/80Make sure to process incoming transfer requests when in exponential backoff2021-07-19T10:53:14ZNiko EhrenfeuchterMake sure to process incoming transfer requests when in exponential backoffCurrently new (incoming) transfers are not being processed at all when the service is in exponential backoff mode (see #79).
We should investigate if the broad catch/except could be narrowed down a bit further to at least process the ne...Currently new (incoming) transfers are not being processed at all when the service is in exponential backoff mode (see #79).
We should investigate if the broad catch/except could be narrowed down a bit further to at least process the new transfer such as to move the data from `INCOMING` to `PROCESSING` (in order to give them the correct timestamp) and to report them in the log.VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/79Limit exponential backoff to 15min2021-07-19T10:53:14ZNiko EhrenfeuchterLimit exponential backoff to 15minIn case an `unhandled exception in OnTimedEvent` occurs (happens e.g. in case the target path is not reachable due to network issues), the service follows an exponential backoff strategy, rapidly increasing the waiting time until the nex...In case an `unhandled exception in OnTimedEvent` occurs (happens e.g. in case the target path is not reachable due to network issues), the service follows an exponential backoff strategy, rapidly increasing the waiting time until the next attempt is being made.
Unfortunately after four steps this already means it will wait for 2 hours and 46 minutes which is not really a practical value. Therefore this should be limited to something like 15 minutes.
**NOTE**: please also see the related issues for more things to consider on this issue!VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/78Report user account when starting tray app2021-07-19T10:40:06ZNiko EhrenfeuchterReport user account when starting tray appFor debugging purposes it can be useful to see in the logs which user is actually running the tray application.For debugging purposes it can be useful to see in the logs which user is actually running the tray application.VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/77Clean up empty folders in the spooling directories.2021-07-19T10:39:59ZNiko EhrenfeuchterClean up empty folders in the spooling directories.When cleaning up the spooling location on a computer it is very annoying having to check all the user directories in the `DONE` folder.
The service could just remove those ones that are emtpy.When cleaning up the spooling location on a computer it is very annoying having to check all the user directories in the `DONE` folder.
The service could just remove those ones that are emtpy.VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/76Allow a marker file on the target storage to suspend all running transfers.2021-07-19T10:53:14ZNiko EhrenfeuchterAllow a marker file on the target storage to suspend all running transfers.This would be particularly helpful in situations where the target location is known to be not available for a certain period (like rebooting the file server(s) or similar).
It also needs to be taken into account that when e.g. the file ...This would be particularly helpful in situations where the target location is known to be not available for a certain period (like rebooting the file server(s) or similar).
It also needs to be taken into account that when e.g. the file server(s) hosting the target location are rebooting the file won't be visible to the service, so it should remember that state ("suspended") and only leave it once it can
1. reach the target location
1. the marker file is NOT present any more
**NOTE**: please also see the related issues for more things to consider on this issue!https://git.scicore.unibas.ch/vamp/auto-tx/-/issues/75Consider a generic super-class for all objects that should only be updated af...2019-05-02T13:01:54ZNiko EhrenfeuchterConsider a generic super-class for all objects that should only be updated after a minimum deltaCurrent code has quite several objects (or even just variables at the moment) that are not supposed to be updated except if a specific amount of time since their last update has elapsed. Instead of having to carry along specific timestam...Current code has quite several objects (or even just variables at the moment) that are not supposed to be updated except if a specific amount of time since their last update has elapsed. Instead of having to carry along specific timestamp variables for each status variable we could try to have this covered by a base class from which all these status variables (converted objects) are derived.
**NOTE**: this might interfere with the XML serialization stuff as some of those classes can't be subclassed / inherited from.Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/74Report logged on user in log file2019-05-02T11:50:53ZNiko EhrenfeuchterReport logged on user in log filehttps://git.scicore.unibas.ch/vamp/auto-tx/blob/master/ATxCommon/SystemChecks.cs#L105
If this turns out to be difficult (or slow) through the `ManagmentObject` queries we could consider checking for existing `explorer.exe` processes, e....https://git.scicore.unibas.ch/vamp/auto-tx/blob/master/ATxCommon/SystemChecks.cs#L105
If this turns out to be difficult (or slow) through the `ManagmentObject` queries we could consider checking for existing `explorer.exe` processes, e.g. like this:
```csharp
foreach (System.Management.ManagementObject Process in Processes.Get())
{
if (Process["ExecutablePath"] != null &&
System.IO.Path.GetFileName(Process["ExecutablePath"].ToString()).ToLower() == "explorer.exe" )
{
string[] OwnerInfo = new string[2];
Process.InvokeMethod("GetOwner", (object[])OwnerInfo);
Console.WriteLine(string.Format("Windows Logged-in Interactive UserName={0}", OwnerInfo[0]));
break;
}
}
```VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/73Be more lenient before sending notifications on network path errors2024-02-21T13:15:21ZNiko EhrenfeuchterBe more lenient before sending notifications on network path errorsOccasionally (maintenance, ...) the target location can't be contacted due to network timeouts or similar, resulting in a message like this:
```
The network path was not found
```
It should be checked if this specific error can be caug...Occasionally (maintenance, ...) the target location can't be contacted due to network timeouts or similar, resulting in a message like this:
```
The network path was not found
```
It should be checked if this specific error can be caught and the corresponding notification could be delayed until this happens for a few attempts in a row to prevent an email flood when e.g. a file server is rebooted and therefore not available.VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/71Add AutoTxConfigTest command line option to report storage status2019-04-29T13:44:52ZNiko EhrenfeuchterAdd AutoTxConfigTest command line option to report storage statusIt would be nice to have `AutoTxConfigTest.exe` report the storage status after a configuration has been successfully parsed.
It's important to keep this optional, as the tool can be used to verify a set of configuration files on any ho...It would be nice to have `AutoTxConfigTest.exe` report the storage status after a configuration has been successfully parsed.
It's important to keep this optional, as the tool can be used to verify a set of configuration files on any host - not just the actual ones they (config files) are meant for. Running the storage status check on another machine doesn't make sense though.
Another option could be to integrate this into the diagnostics tool, however then it would be mandatory to read the configuration from there - this is open for discussion!
No matter where it will be implemented, we definitely need proper command line parsing then - see the [related bookmarks in the wiki](https://git.scicore.unibas.ch/vamp/auto-tx/wikis/Development-Bookmarks#command-line-argument-parsing) for details.VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/70Show storage status details in tray menu2019-04-28T22:04:08ZNiko EhrenfeuchterShow storage status details in tray menuSee #20 for details on the storage status. See #20 for details on the storage status. VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/69Allow users to clean their own folders from grace location2019-04-28T19:58:40ZNiko EhrenfeuchterAllow users to clean their own folders from grace locationVAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/68Show human name of transfer target in tray menu2019-04-26T09:01:16ZNiko EhrenfeuchterShow human name of transfer target in tray menuJust noticed the tray app doesn't say *where* data will be transferred to, so this might be confusing to users that are not familiar with the app (since they don't have any hint what this thing is supposed to do).
Just add the name of t...Just noticed the tray app doesn't say *where* data will be transferred to, so this might be confusing to users that are not familiar with the app (since they don't have any hint what this thing is supposed to do).
Just add the name of the target location in the menu entry should already help a lot.VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/67Support more than one target location2019-04-23T22:13:20ZNiko EhrenfeuchterSupport more than one target locationhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/66Send a notification on long system uptimes2019-04-23T22:07:22ZNiko EhrenfeuchterSend a notification on long system uptimesWhile many people consider long uptimes as a sign of quality, reality has proven many many times that rebooting a system is a good idea to keep it running smoothly.
Hence the service could send a notification if a host has not been boot...While many people consider long uptimes as a sign of quality, reality has proven many many times that rebooting a system is a good idea to keep it running smoothly.
Hence the service could send a notification if a host has not been booted for a given time.VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchterhttps://git.scicore.unibas.ch/vamp/auto-tx/-/issues/63Catch serialization errors when writing status file2019-04-18T09:38:18ZNiko EhrenfeuchterCatch serialization errors when writing status fileOccasionally, the status file can't be written. Error messages is as follows:
```
[Error] Error in Serialize(): The process cannot access the file 'C:\Tools\AutoTx\var\status.xml' because it is being used by another process.
```
Instea...Occasionally, the status file can't be written. Error messages is as follows:
```
[Error] Error in Serialize(): The process cannot access the file 'C:\Tools\AutoTx\var\status.xml' because it is being used by another process.
```
Instead of logging an error directly, we could have a counter and have the service try to rewrite the status file as soon as that counter is above zero even if the status hasn't changed. Only if the counter is above a threshold (2?) an error should be logged (and therefore an email be triggered).VAMP AutoTransfer v3Niko EhrenfeuchterNiko Ehrenfeuchter