Code completion randomly fails
Issue #937
resolved
Apex code completion randomly fails. This has been going on for a while now and happened in IC 1 and now also in 2. At first code completion works like a charm after generating the offline symbol table.
Then, suddenly code completion doesn't work anymore. When starting to type a Class or SObject name I still get suggestions but I don't get any suggestions when looking for methods.
Example: I want to have the System.RunAs
I select System and hit the dot (.). No methods show up.
After regenerating the Offline Symbol table code completion works again.
Comments (8)
-
repo owner
-
Account Deactivated reporter
I already enabled logging. As soon as it happens I will ad them to the case.
[image: Logo Appsolutely] http://www.appsolutely.nl * JAAP BRANDERHORST* +3 16 10 00 17 14 <+31610001714> <0031652819644> APPSOLUTELY.NL http://www.appsolutely.nl http://www.appsolutely.nl [image: LinkedIn] https://www.linkedin.com/company-beta/17912349/ [image: Twitter] https://twitter.com/Appsolutely_SF
-
repo owner
Potentially related to
#927? -
Account Deactivated reporter
- attached idea.log.2
- attached idea.log.1
- attached idea.log
Debug logs. It happened again.
-
repo owner
Thanks, Jaap. I can see the issue itself. I'll try to use this to track down the root cause. It looks like I have some issue with elements going stale again. Hopefully I can get a fix in the next build.
-
repo owner
I've made some progress on this, but my guess is that it's not a root cause fix. It should hopefully help address the way things are handled if/when they get into this state. I'm going to keep investigating and try to trap the situation when it's happening so I can get that real root cause. I'll include the progress I've made in the Monday build.
-
repo owner
Progress on this delivered in 2.0.1.4. As noted above, I've set things up so that as soon as this happens to me in my main project, I should be able to connect a debugger and get to the bottom of it for a full fix.
-
repo owner
- changed status to resolved
Issue tracker grooming. If this is still an issue, please feel free to reopen, ideally with a concrete reproduction scenario.
- Log in to comment
Jaap, it sounds like something in the caches/indices is "decaying" over time, and OST generation rebuilds the indices at completion which would explain why it remedies the problem. The next time this begins to occur, would you mind capturing your logs and sending them to me so I can hopefully see how it starts?