Closed eapearson closed 6 years ago
Sorry - I cannot comment on the scanning issue. I know to little about this. What I do remember is, that pegdown has "problems" with a lot of consecutive [
. See https://github.com/sirthias/pegdown/issues/104. The API.md file looks pretty similar to the log example in this issue.
So I believe the org.pegdown.ParsingTimeoutException
is expected behaviour :S . There is currently a lot of "merging pull requests" going on at pegdown - so maybe it would be a good time to talk to the pegdown people about this.
Thanks, that looks like it may be similar, although I don't think the API.md file has deeply nested opening characters. However, it is fairly complex and liberal with the usage of special characters, although it does render and validate in other apps, so I suspect pegdown is confused or not forgiving enough with markdown (ab)use. Frankly, this has me now looking for another IDE :( I've become devoted to Netbeans, but the thought that something as straightforward as a markdown file can bring the IDE to a halt, and require hours of debugging is just not something I need in my work life.
You could still disable or uninstall the Markdown plugin until this issue is resolved. Depending on how familiar your are with NetBeans and other IDEs this may be more efficient than learning another IDE.
At least this Markdown plugin for IntelliJ IDEA is also based on the pegdown library. It therefore may suffer from the same problem.
Good call! I downloaded intellij, opened up API.md, installed the plugin, and not only did intellij hang, but took 6 cores along with it. At least NB only took 2 :) My current workflow involves markdown documentation alongside api-building and sample programs, so I don't want to disable the otherwise wonderful markdown plugin for the sake of one problematic file. Ideally I'd like to just blacklist that one file, which I'll pursue with the netbeans folks. BTW I spent just a few minutes with Aptana and Intellij and will stick with NB. I'm sure they are fine once you learn them, but I found that I'm not ready to throw out NB and friends just yet. Thanks for paying attention to this.
After including a new dependency in my project, Netbeans went haywire, getting stuck in in project scanning. Not only is the source scanner notification stuck at 100% (or something else on test projects), but the interface becomes sluggish, and my laptop goes into a tailspin.
Running NB with the
I found that the scanner was stopping on one markdown file, like so:
This file is actually API.md from the bluebird javascript library. Viewing the file causes NB to hang, but I'm able to whittle it down until I start receiving error dialogs with the content as below. (Note that the error is not emitted until I add a small bit of text on line 574, parsers!)
So a solution? For now I've excluded bower_components from NB using the preferences.
I would rather like to be a bit more specific about excluding problematic files from the scanner. Does anyone know if there is a configuration for this? (I see that the scanondemand plugin has such a setting.)
Anyway, back to this issue. Is this an issue that is appropriate for the NB markdown plugin or directly with the pegdown folks? It is starting to get a little far afield from what I should be doing with my work time...