Sorry I don't have more specific repro steps - this occurs when retrieving diagnostics for every TypeScript file in our workspace via the Eclipse plug-in. Hopefully the stack trace is enough to determine the issue.

file attachments

comments

Thanks for reporting this. It's not clear how the compiler got into this state, but we have some tools we can run to try to reproduce the issue that we can run if you could upload the file(s) you were working on when you got this. We do a lot of fuzzing-type
edits on the language service and have never seen this, so there may be something special in the codebase that we need to test on.

As always, please "re-open" the issue if you can provide more information. Thanks!

I don't think I'll be able to provide the entire code base but I could send the single file that seems to trigger this issue. I'd prefer not to upload it publicly though - is there an email address where I could send it?

Ok, I dug into this a bit more and I think I can see why this might be failing now: this is somewhat "special" call.

The code causing the exception looks like this:

public static create(renderer, xscale, yscale, renderers, datasets, intrabarPadding: any = 25) {
// A Renderer is a class that given a graphical context,
// a set of scales, and a series of data, draws nice charts
// onto a plot.
if (this.classes[renderer.type] != null) {
return new this.classes[renderer.type](renderer, xscale, yscale, renderers, datasets, intrabarPadding);
}
}

Does this provide enough information to figure out how to fix it or do you need more context?