-
Notifications
You must be signed in to change notification settings - Fork 358
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
unable to spider - fails on imported config check #498
Comments
The exact same error is happening for me and I am only running against current production domain. I tried using both the capture.yaml and the spider.yaml config files with same result. |
I am have this same issue with the default spider.yaml config files.
|
Same here
It would appear that this commit was intended to fix this very same issue: a8c968a Adding a spider_paths.yaml file in the
|
Thank you @pcambra It solved the issue for me. |
Fails for me with following: wraith spider spider.yaml DEBUG: ################################################# |
I commented this section out of spider.yaml and now it works for - future reference I noticed in issue #401 that this was similar issue: spider_skips:- /foo/bar.html # Matches /foo/bar.html explicitly- !ruby/regexp /^/baz// # Matches any URLs that start with /baz |
This should now be fixed in v4.0.1. |
@ChrisBAshton, I just installed version 4.0.1 using brew, but to get spider working, I had to add config/spider_paths.yml (thank you, @pcambra) and comment out the spider_skips (thank you, @mramitanand), so this issue does not seem to be fixed. |
I am trying to run
wraith spider
and have it build my paths file, but it is failing when it is not able to find thespiders_paths.yaml
file.I see this error:
It should create this file if it does not exist, correct?
Reporting a problem? Please describe the issue above, and complete the following checklist so that we can help you more quickly.
Issue checklist:
I have validated my config file against YAML Validator to make sure it is valid YAML.
I have run the
wraith info
command and pasted the output below:verbose: true
to my config) and pasted the output below:The text was updated successfully, but these errors were encountered: