Skip to content
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.

Sign up for GitHub

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

Jump to bottom

gOSINT will crash if the configuration file doesn't exist #12

Open
Nhoya opened this issue Apr 1, 2018 · 1 comment
Open

gOSINT will crash if the configuration file doesn't exist #12

Nhoya opened this issue Apr 1, 2018 · 1 comment
Assignees
@Nhoya
Labels
bug help wanted

Comments

@Nhoya
Copy link
Owner

Nhoya commented Apr 1, 2018

This is a bug relative to viper the current SafeWriteConfigAs is broken and I hope will be fixed ASAP, since this is relative only to the develop version of gOSINT i'll wait for spf13/viper#450 to be approved
@Nhoya Nhoya self-assigned this Apr 1, 2018
@Nhoya Nhoya added the bug label Apr 1, 2018
@Nhoya
Copy link
Owner Author

Nhoya commented Nov 1, 2018 •
edited

The Issue is currently mitigated in development creating a dummy configuration file if it doesn't exist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Nhoya Nhoya

Labels
bug help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Nhoya