Stack overflow w/ angular_ast at 0.4.0-alpha+2

[dart-lang]

Stack overflow w/ angular_ast at 0.4.0-alpha+2

[kevmoo]

CC @isoos

[kevmoo]

Likely a pkg/analyzer issue – keeping this for tracking

[kevmoo]

Ran against pkg/analyzer (and front_end and kernel) from dart-lang/sdk@5b95582

No issue.

Wondering if this is something that has been fixed...

[kevmoo]

Also w/ pkg/linter @ 0.1.39

[isoos]

Also w/ pkg/linter

Also gets fixed with the bleeding edge SDK?

[kevmoo]

Also gets fixed with the bleeding edge SDK?

Not sure.

[isoos]

I the linter's case there was something in-between 0.1.34 and 0.1.35 that triggers the error.

[isoos]

It looks like analyzer goes into a cycle here: https://github.com/dart-lang/sdk/blob/master/pkg/analyzer/lib/src/context/cache.dart#L812

Probably the cache entry's dependent results go into a cycle, which may be valid, but it is not guarded for re-entry there. What is the best way to get a change accepted there?

[kevmoo]

@isoos So I checked 3 packages w/ pana @ master and then using the latest alpha analyzer

Fixes 2 out of three.

We'd have to wire up a dependency_override on the production deployment. Thoughts?

+
+dependency_overrides:
+  analyzer: 0.31.0-alpha.2

stack overflow
dart bin/main.dart angular_analyzer_plugin

• fixed!

AnalysisException: Cannot compute LIBRARY_ELEMENT
dart bin/main.dart dart2ts

• fixed!

AnalysisException: Element mismatch
dart bin/main.dart jsonx

• still broken! @ jsonx v2.0.2

[isoos]

can't we just depend on the 0.31.0-alpha.2 directly?

[kevmoo]

It'll blow up w/ a dependency conflict w/ pkg/test

Need to use a dependency override

[kevmoo]

Can't do anything until we can publish a version that depends on a ^0.31.0 gold release of analyzer.

[isoos]

Closing this here, as the pubspec.yaml is already updated (although not yet published).