Skip to content
This repository has been archived by the owner on Nov 4, 2024. It is now read-only.

--rescan always returns Error:recent-scan-not-found #27

Open
april opened this issue Oct 24, 2016 · 4 comments
Open

--rescan always returns Error:recent-scan-not-found #27

april opened this issue Oct 24, 2016 · 4 comments
Labels
bug help wanted needs-info

Comments

@april
Copy link

april commented Oct 24, 2016

Even though it does seem to successfully execute another scan.
@gregglind gregglind added the bug label Oct 31, 2016
@gregglind
Copy link
Contributor

Okay, I will look into this!

@gregglind
Copy link
Contributor

Sorry for this, what was your example? having trouble reproducing.

@april
Copy link
Author

april commented Nov 1, 2016

If I run:

$ observatory pokeinthe.io

(wait a few)

$ observatory --rescan pokeinthe.io

It simply outputs recent-scan-not-found, even though it did actually do another scan.

@gregglind
Copy link
Contributor

Weird. I am unable to reproduce under 0.7.1. I might recommend:

observatory --version
NODE_DEBUG=request observatory pokeinthe.io

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug help wanted needs-info
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gregglind @april