Community
Participate
Working Groups
M9 build. Occurred while editing from background task. See attached error log and screeshot.
Created attachment 10985 [details] Error / Configuration log
Created attachment 10986 [details] Error message This was shown several times in succession.
I regret that I do not have precise recreation steps. I had very recently selected "Source > Sort Members" when this happened. The "Mark Occurrences" options are all checked and it may be related (it displayed a warning message saying all of these marks would be lost).
I propose to replace all the try/catch AbortCompilation with try/catch RuntimeException inside the DefaultBindingResolver. I believe this is another case of errors when the compilation unit has been reset. Could you please attach your test case? I'd like to be able to reproduce the problem and be sure that the suggested fix is right.
As I said in comment #3, I regret that I don't have a testcase and I can't reproduce it on demand. Normally I wouldn't bother reporting it, but since the 3.0 ship date approaches, I have reported spurious errors even if I can't reproduce them as long as there's a decent log.
You were perfectly right. It is always good to report problems. If you get a test case, don't hesitate to attach it. Thanks for the report. I will try to investigate.
I will add a try/catch RuntimeException where I had a try/catch AbortCompilation in order to catch cases where the scopes are not available anymore.
Fixed by catching RuntimeException. This seems to be a case where no scopes are available anymore. If we change our strategy of removing scopes at the end of the DOM/AST creation I will revisit this one. Fixed and released in HEAD.
Could not reproduce. No test case available, but the try/catch should handle that case now. Verified in 200405281200. Please reopen if you see it with a newer build.
