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.

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

refresh cscope-db reports Error: Unable to refresh cscope database #5

Closed
davy79 opened this issue Dec 10, 2015 · 4 comments
Closed
Assignees
Labels

Comments

@davy79
Copy link

davy79 commented Dec 10, 2015

Unfortunately the refresh-db command reports Error: Unable to refresh cscope database.

Running ubuntu 14.04 with cscope running from the command line.
Atom 1.2.4

Is there any other debug info I can provide?

@amitab
Copy link
Owner

amitab commented Dec 10, 2015

If this fails, some object would have been printed in the console.
Example:
Object {success: false, message: "At /home/amitabh/src/mysql-router: find: paths mus…arch|stat|rates|opt|exec] [path...] [expression]↵"}
The attribute: message would contain the reason why it failed. Can you paste that here?

@davy79
Copy link
Author

davy79 commented Dec 10, 2015

hmmm, I got this...

ReferenceError: fs is not defined
    at /home/jda/.atom/packages/atom-cscope/lib/cscope.coffee:20:7
    at Object.module.exports.CscopeCommands.writeToFile (/home/jda/.atom/packages/atom-cscope/lib/cscope.coffee:19:16)
    at /home/jda/.atom/packages/atom-cscope/lib/cscope.coffee:31:17
    at process._tickCallback (node.js:368:9)

@amitab amitab added the bug label Dec 11, 2015
@amitab amitab self-assigned this Dec 11, 2015
@amitab
Copy link
Owner

amitab commented Dec 11, 2015

Resolved in 42ffebf
Please check the new release and let me know if the same problem persists. Honestly I have no idea why it was working for me even though the variable fs was not declared.

@amitab amitab closed this as completed Dec 11, 2015
@davy79
Copy link
Author

davy79 commented Dec 12, 2015

Verified!

Everything works fine now!

It's a common problem that something works on our own machine 😄
most common response from the dev after receiving a bug report: "works for me"

At work we always test on a clean virtual machine before release to avoid such common issue.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants