fmt.Printf("hello") was working great with intellisense
but suddenly in every go file my fmt.P .. suggestion becomes this
and this
I am not getting "fmt.Printf()" suggestions anymore and getting stuck with those "const", "func", "import", "type", & "var".. what is happening? (Though it is not suggesting fmt.Printf() but it's still working). how can I get normal suggestions by intellisense like previous?
I tried disabling GO official extension, then it got fixed but also I lose all autocomplete/suggestion feature. a go file in root directory is working fine but other files inside packages are showing this kinda problems. Please help
After searching a lot I couldn't find exact problem and solution. And somehow I saw some were facing "case-insensitive import collision:" and it was due to upper-case and lower-case mixture usage in filename. I remembered it seeing in my package name (though this error vanishes sometimes and ignored it as code execution was working) and tried renaming my filename from "sequenceUtils.go" to "sequence_utils.go" and boom ..! intellisense started working ..! though my colleague was working with same filename and he wasn't facing problems..
I think the problem should be properly identified..!
Related
I'm having issues with my integrated terminal in vs code. It has multiple cursors in weird placed when inputing text. I have tried reinstalling vs code and the issue wasn't solved. I also tried modifying the settings.json which also didn't help. I will appreciate any help given.
I know that a similar was asked on Intellisense not working golang test files, but since I am new to VS Code I didn't quite understand the solution. Also since I have a low reputation I couldn't comment for help.
What I know about my problem is that on Ctrl + Space VSCode used to show the list of functions associated with the Golang package, but suddenly one day it stopped working.
Okay, I found out my answer. Apparently for some reason in my settings.json the line "go.useLanguageServer": true, wasn't there. After adding it VSCode told me to install something called gopls which fixed everything.
I'm starting to work on a small firefox plugin, it's a basic js script, no problem on this side.
I've made a few successfull tests, and had a a few satisfying results. But starting yesterday, i'm unable to laod any temporary addons in firefox.
Everytime i try to start one (even a simple console.log("hello world")), i get the error message in the console:
Error: Can't find profile directory. XULStore.jsm:66:15
It work perfectly 2 days ago, the problem appeared yesterday, and, as far as i know, i didn't made any firefox upgrade.
I've made a few reseach, a found two usefull links, one on discourse.mozilla of someone that has the exact same problem ... but no answer, and another one on bugzilla saying this bug won't be fixed because it should last long ... https://bugzilla.mozilla.org/show_bug.cgi?id=1548017
I'm askign here because i can't find any solution to my problem, and right now, it's been 24h since i'm stuck in my development progress. I'm open to any suggestion that might work.
I've checked my profiles directory and files, they're existing and ok... and that's basically everything. I'm not familiiar with the tools available for firefox so, i might have forgotten to check basic things that might help.
P.S: i'm not using selenium at any time (i've seen a few requests here about a similar issue with selenium, but i'm writing vanilla JS here, so, i think it's not the same issue)
Our system is using compass to compile sass files. Following the same workflow as usual today when I run compass compile there is a long pause followed by "killed" with no errors or warning.
I'm not even sure how to troubleshoot this issue. Has anyone else run into a similar problem? If so, how did you solve it?
Thank you in advance...
update
I have been through the code and I cannot find a pattern to it not compiling. After making a minor change it compiled successfully making another minor change it failed. Each time I believe the problem is resolved, I make a change that's very small in scope and it breaks it again... for example removing and id (#main) from a definition stops the compile... putting it back does not fix the problem... adding a comment fixes the problem... remove it and it stays fixed, until I make another change .... I've matched my braces and gone over every change made in the last 3 days... I cannot find a cause for the error, or why its not behaving consistently
If other commands on the server die with a "Killed" error message, it could be a resource issue. Check your server logs for out of memory errors.
When working on a large Firefox plugin, I sometimes accidentally make a syntax error not caught by my editor. When this happens, then calling
Components.utils.import("resource://modules/Foo.js")
will simply fail to import or return anything, without any kind of helpful hint as to where in the file to look for the syntax error. Is there any way I can get Firefox to give me some kind of clue when my imports fail?
EDIT: I fixed my own problem, which turned out to be that I was using code which had a global reference to the navigator object. What made this especially annoying was that the code would work when loaded in the browser (as Wladimir suggested below), but would still fail when importing in my extension.
Eventually I resorted to a sort of manual binary search: I'd delete half of the file and then see whether the import still failed. If so, then I'd delete half of what remained and repeat. As soon as it didn't fail, I had a more precise notion of where the problem was, which allowed me to either continue the binary search or scan the smaller area manually looking for the problem.
This is extremely time-consuming and I'd still appreciate any suggestions about how to speed up this debugging process.
The issue here is most likely the one described on https://developer.mozilla.org/en/Exception_logging_in_JavaScript and setting dom.report_all_js_exceptions preference to true should work. I must admit that I haven't tried that however because setting this preference makes the error console very noisy. Instead I use an ugly hack and load the module as a script in a local HTML file - this is enough to show me syntax errors and fortunately isn't something I need to do all too often (it is only an issue with syntax errors, runtime errors are reported as usually).