-
Notifications
You must be signed in to change notification settings - Fork 287
wrong file reference on not existing drive #251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for the report, @Stingra-VI! For the the The exception looks like it's trying to access |
Thank you for the report @Stingra-VI. I'm able to reproduce this behavior. I'll post a fix by the end of the week that will error out before running the full comparisons if the path doesn't exist. Is having the path automatically created an important feature for you? It is something I can investigate but is more difficult because ASA runs as Admin/Root and it is obviously undesirable to create an admin owned directory. |
Fix pushed. Thanks again for your report @Stingra-VI. |
Dear Gabe,
Thank you so much for his quick fix and keeping me up to date.
We are just starting with ASA, so it is highly appreciated :)
Best regards
Markus
Am 13. August 2019 08:39:14 MESZ schrieb Gabe Stocco <[email protected]>:
…Fix pushed. Thanks again for your report @Stingra-VI.
<img width="1375" alt="Screen Shot 2019-08-12 at 11 38 10 PM"
src="https://user-images.githubusercontent.com/98900/62920329-4c84f900-bd5a-11e9-9d33-bc34f425417b.png">
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#251 (comment)
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
|
Describe the bug
running a report on a not existing directory shows a wrong drive reference.
I would like to point out that this is my first MS "bug" report. If I forget more details, please get back to me.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
2 attached
System Configuration (please complete the following information):
Additional Context
after creating that directory the command works as expected
The text was updated successfully, but these errors were encountered: