Skip to content

Editor log file with some exceptions #612

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

Closed
floitschG opened this issue Nov 28, 2011 · 6 comments
Closed

Editor log file with some exceptions #612

floitschG opened this issue Nov 28, 2011 · 6 comments
Assignees
Labels
closed-invalid Closed as we don't believe the reported issue is generally actionable

Comments

@floitschG
Copy link
Contributor

I'm resetting my editor-workspace (thus removing my log-file).
In case you want to go through the exceptions I have attached the log-file.


Attachment:
.log (209.32 KB)

@jwren
Copy link
Member

jwren commented Nov 29, 2011

This stack trace has errors coming out of a few Dart Editor classes including CompilerListener, UrlSource, and 2 locations in the DeltaProcessor.

It looks like Florian, was trying to edit classes in frog.

I tried to reproduce his issues, but was unable to load Frog into my runtime (svn version 1878).

  • Jaime

@floitschG
Copy link
Contributor Author

Same procedure as yesterday: upgrading my editor and submitting the log-files before wiping.
If you prefer not to receive these log-files or want them in another bug, please tell me.


Attachment:
.log (549.26 KB)

@keertip
Copy link
Contributor

keertip commented Nov 29, 2011

Florian,

Are you restting the workspace because you are having problems or is it just procedure when you upgrade?

The messages in the log relate to compiler not being able to compile node.dart, not much we can do there.

@floitschG
Copy link
Contributor Author

standard procedure. There is not yet much state in the workspace directory, and I prefer to have a clean directory when submitting bug-reports.

@bwilkerson
Copy link
Member

I suspect that the problems indicated by these log entries have either been fixed or that the log entries are no longer of value because the code base has changed so much since the logs were captured. I would recommend closing this issue.


Set owner to @danrubel.

@danrubel
Copy link

danrubel commented Feb 1, 2012

Agreed. Closing.


Added Invalid label.

@floitschG floitschG added Type-Defect closed-invalid Closed as we don't believe the reported issue is generally actionable labels Feb 1, 2012
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-invalid Closed as we don't believe the reported issue is generally actionable
Projects
None yet
Development

No branches or pull requests

5 participants