Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Exception in visitConstructor #18190

Closed
lukechurch opened this issue Apr 12, 2014 · 8 comments
Closed

Exception in visitConstructor #18190

lukechurch opened this issue Apr 12, 2014 · 8 comments
Assignees
@lukechurch
Labels
area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. closed-obsolete Closed as the reported issue is no longer relevant

Comments

@lukechurch
Copy link
Contributor

1.3.0.dev_07_05 (2014-03-28) : Exception

Probable last version: 1.3.0.dev_07_05 (2014-03-28)
ClusterID: 934afe78
Date: 2014-04-11, count: 9
Date: 2014-04-10, count: 1
Date: 2014-04-10, count: 1
java.lang.Exception
    at com.google.dart.engine.internal.resolver.ScopedVisitor.visitConstructorDeclaration(ScopedVisitor.java:311)
    at com.google.dart.engine.internal.resolver.TypeResolverVisitor.visitConstructorDeclaration(TypeResolverVisitor.java:306)
    at com.google.dart.engine.internal.resolver.ScopedVisitor.visitConstructorDeclaration(ScopedVisitor.java:1)
    at com.google.dart.engine.ast.ConstructorDeclaration.accept(ConstructorDeclaration.java:153)
    at com.google.dart.engine.internal.resolver.TypeResolverVisitor.visitClassDeclarationInScope(TypeResolverVisitor.java:790)
    at com.google.dart.engine.internal.resolver.ScopedVisitor.visitClassDeclaration(ScopedVisitor.java:277)
    at com.google.dart.engine.internal.resolver.TypeResolverVisitor.visitClassDeclaration(TypeResolverVisitor.java:236)
    at com.google.dart.engine.internal.resolver.ScopedVisitor.visitClassDeclaration(ScopedVisitor.java:1)
    at com.google.dart.engine.ast.ClassDeclaration.accept(ClassDeclaration.java:127)
    at com.google.dart.engine.ast.NodeList.accept(NodeList.java:67)
    at com.google.dart.engine.ast.CompilationUnit.visitChildren(CompilationUnit.java:216)
    at com.google.dart.engine.ast.visitor.UnifyingAstVisitor.visitNode(UnifyingAstVisitor.java:367)
    at com.google.dart.engine.ast.visitor.UnifyingAstVisitor.visitCompilationUnit(UnifyingAstVisitor.java:123)
    at com.google.dart.engine.ast.CompilationUnit.accept(CompilationUnit.java:110)
    at com.google.dart.engine.internal.resolver.LibraryResolver2.buildTypeHierarchies(LibraryResolver2.java:414)
    at com.google.dart.engine.internal.resolver.LibraryResolver2.resolveLibrary(LibraryResolver2.java:194)
    at com.google.dart.engine.internal.task.ResolveDartLibraryCycleTask.internalPerform(ResolveDartLibraryCycleTask.java:109)
    at com.google.dart.engine.internal.task.AnalysisTask.safelyPerform(AnalysisTask.java:119)
    at com.google.dart.engine.internal.task.AnalysisTask.perform(AnalysisTask.java:73)
    at com.google.dart.engine.internal.context.AnalysisContextImpl.performAnalysisTask(AnalysisContextImpl.java:1788)
    at com.google.dart.tools.core.internal.builder.AnalysisWorker.performAnalysis(AnalysisWorker.java:386)
    at com.google.dart.tools.core.internal.builder.AnalysisManager.performAnalysis(AnalysisManager.java:135)
    at com.google.dart.tools.core.internal.builder.AnalysisManager$1.run(AnalysisManager.java:167)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
@clayberg
Copy link

Added this to the 1.4 milestone.
Removed Priority-Unassigned label.
Added Priority-High label.

@bwilkerson
Copy link
Member

This is an informational message in the log that happens to have a stack trace for context. (In other words, no exception is being thrown.)

But when the informational message is generated there is additional message text that is not included in the information in this issue. Specifically, we're invoking the method Logger.logInformation(String message, Throwable exception) and the message is not included above.

It looks like this message is getting passed on to instrumentation, but it's being lost somewhere (perhaps in the code that's grouping exceptions). My hope was that this message might give us enough information to be able to figure out how to reproduce the underlying problem. Let's talk about what can be done to get access to the message.

Set owner to @lukechurch.
Removed Priority-High label.
Added Priority-Medium label.

@bwilkerson
Copy link
Member

Added NeedsInfo label.

@kasperl
Copy link

kasperl commented May 8, 2014

Removed this from the 1.4 milestone.
Added this to the 1.5 milestone.

@kasperl
Copy link

kasperl commented Jun 4, 2014

Removed this from the 1.5 milestone.
Added this to the 1.6 milestone.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the 1.6 milestone.
Added Oldschool-Milestone-1.6 label.

@kasperl
Copy link

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-1.6 label.

@bwilkerson
Copy link
Member

Added AssumedStale label.

@lukechurch lukechurch added Type-Defect area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. closed-obsolete Closed as the reported issue is no longer relevant labels Feb 25, 2015
@lukechurch lukechurch self-assigned this Feb 25, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lukechurch lukechurch

Labels
area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. closed-obsolete Closed as the reported issue is no longer relevant
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kasperl @lukechurch @bwilkerson @clayberg