String parsing/error-highlighting bug in Diana

There is already a JIRA issue filed for this (IDEA-18037), however it is listed as a low-priority bug. After I had upgraded to Diana, I am finding that a small number of my string constants (primarily, some strings that define regular expression patterns) in various classes and projects are showing up highlighted as errors. Not all regex patterns are misinterpreted, of course, and many of complex patterns are treated correctly. However, some show up highlighted. I ahve attached a screenshot to the issue in JIRA. Although the projects still build ok, it looks dirty to have files in my projects that are error-highlighted for no reason. Needless to say, it becomes confusing to tell which class indeed contains a legitimate compilation error.

I see that issue IDEA-18037 was originally filed in May, and it has not been addressed yet. Perhaps, it is due to the fact that the priority was set to "low" by the reporter, and, possibly, due to the misleading description that implied that the issue might have to do with SQL strings in prepared statements, specifically. The latter, clearly, is not the case, since it seems to be a general string parsing problem in Diana. I think the issue must be upgraded to a higher priority and attended ASAP.

Thanks,
Constantine

3 comments
Comment actions Permalink

Hello constv,

We're well aware of this issue, but unfortunately we don't know of a way
to reproduce it repeatably. This, rather than someone's severity assignment,
is what's blocking us from fixing it.

There is already a JIRA issue filed for this (IDEA-18037), however it
is listed as a low-priority bug. After I had upgraded to Diana, I am
finding that a small number of my string constants (primarily, some
strings that define regular expression patterns) in various classes
and projects are showing up highlighted as errors. Not all regex
patterns are misinterpreted, of course, and many of complex patterns
are treated correctly. However, some show up highlighted. I ahve
attached a screenshot to the issue in JIRA. Although the projects
still build ok, it looks dirty to have files in my projects that are
error-highlighted for no reason. Needless to say, it becomes confusing
to tell which class indeed contains a legitimate compilation error.

I see that issue IDEA-18037 was originally filed in May, and it has
not been addressed yet. Perhaps, it is due to the fact that the
priority was set to "low" by the reporter, and, possibly, due to the
misleading description that implied that the issue might have to do
with SQL strings in prepared statements, specifically. The latter,
clearly, is not the case, since it seems to be a general string
parsing problem in Diana. I think the issue must be upgraded to a
higher priority and attended ASAP.

Thanks,
Constantine

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Dmitry,
thanks for the response. I did not realize that the examples provided in the JIRA ticket do not produce the same errors in other IDEA installations. Is it what you are saying? After I read your reply I tried to move one of my wrongly highlighted regex strings from one file to another, and realized that the same string that was wrongly highlighted in one file, was parsed just fine in another! Moving the string definition within the same file did not eliminate the highlighting. I see now that it is obviously not a trivial issue. So, it is a file parsing issue then... Interesting bug, anyway!

Thanks,
Constantine

0
Comment actions Permalink

Hello constv,

The problem is (at least partly) a race condition. It happens intermittently
even on the same IDEA installation with the same file.

thanks for the response. I did not realize that the examples provided
in the JIRA ticket do not produce the same errors in other IDEA
installations. Is it what you are saying? After I read your reply I
tried to play move one of my wrongly highlighted regex strings from
one file to another, and realized that the same string that was
wrongly highlighted in one file, was parsed just fine in another!
Moving the string definition within the same file did not eliminate
the highlighting. I see now that it is obviously not a trivial issue.
So, it is a file parsing issue then... Interesting bug, anyway!
Thanks,
Constantine

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Please sign in to leave a comment.