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.

Sign up for GitHub

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

Errors in files outside of project crashes output monitor #17

Open
jarhart opened this issue Sep 17, 2013 · 1 comment
Open

Errors in files outside of project crashes output monitor #17

jarhart opened this issue Sep 17, 2013 · 1 comment
Labels
bug

Comments

@jarhart
Copy link
Owner

jarhart commented Sep 17, 2013

The output monitoring and error tracking assumes errors always come from files in the project. Tests that cause exceptions to be thrown from library files (e.g. None.get throws an exception from Option.scala) crash the output monitor.
@inkytonik
Copy link
Contributor

I've run into this one quite a lot lately. To avoid problems, I've got a local fix to just ignore errors that come from files outside the project so that we don't get crashes. I'm happy to contribute this small fix if there is agreement that ignoring is the right thing to do. (I'm not sure what else we can do.)

inkytonik added a commit to inkytonik/SublimeSBT that referenced this issue Nov 28, 2014
@inkytonik
Ignore errors in files that aren’t in the current project (jarhart#17)
d42905f 
In some cases it is possible for SBT to generate an error that refers
to a file that is not in the local project. E.g., this occurs if you
are using a testing library and the error is actually triggered in
the library rather than in your code. Previously SublimeSBT would
crash in this circumstance since it assumed that the errors always
referred to files in the local project.
@inkytonik inkytonik mentioned this issue Nov 28, 2014
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@inkytonik @jarhart