-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
[bug] unexpected panic when specifying --directory
of a tmpfs
#11
Comments
Hi! The error says TL;DR: Start with an empty directory and then it will be "atac-only". If you think this was a bad idea, it can change without problem :) Merci également |
In that case, perhaps a better error message would help. Additionally it's not stated anywhere in the documentation the requirements for this directory. I'll be honest, I do find this behaviour a bit strange (and concerning). Correct me if I'm wrong, but I get the impression that I won't push the issue further though :-) It's your call if you'd like to keep existing behaviour or make changes, I'm only trying to help! Additional ThoughtsIf it were me, I would organize [core]
log-path = "atac.log"
[collections]
my_collection = "my_collection.json" This has the added benefit that you can separate configuration from runtime files: it's pretty common to see applications use configuration files in the user's If users could put I digress 😅 |
It may seem unclear until you read the code, the application is not parsing anything that is not handleable. So no worries about that. I removed the
Yes it is planned that the config file ( |
Issue Description
When specifying a tmpfs location as an argument to
--directory
, the application panics unexpectedly.I haven't dug any deeper. It should be easily reproducible.
Looks like it should be a quick fix. Cool project! :-)
Merci!
The text was updated successfully, but these errors were encountered: