These are chat archives for ensime/ensime-atom
Check status on Emacs here: http://ensime.github.io/editors/emacs/debugging/
I guess we could imitate this pretty quickly. We should be able to persist breakpoints too: https://discuss.atom.io/t/saving-package-specific-data-on-project/25607
I very seldom debug nowadays, if I have problems I try to reproduce by tests instead. But I actually did debug ensime-server in Eclipse a few weeks ago to try to understand some things though. scala-compiler is probably the worst looking Scala code I've seen so there debugging was needed. :)
There's probably a lot of UI work to make debugging in Atom as good as Eclipse too. I think the stack rewriting smartness of scala-ide isn't in ensime either…
or value seconds is not a member of Int Note: implicit value timeout is not applicable here because it comes after the application point and it lacks an explicit result typeat line 16 col 36 Error could not find implicit value for parameter timeout: akka.util.Timeoutat line 44 col 45 Error not enough arguments for method ?: (implicit timeout: akka.util.Timeout, implicit sender: akka.actor.ActorRef)scala.concurrent.Future[Any]. Unspecified value parameter timeout.at line 44 col 45
All files seen. Starting client connecting on port: 55235 ["changed from ", Object, " to ", Object] client connected ["changed from ", Object, " to ", Object] client.coffee:68 Ensime server error event: Error: This socket is closed.
["changed from ", undefined, " to ", undefined]when I change to a scala file
connecting on port: 55392
DEBUG None o.e.i.SearchService - indexing file:///...
16:27:31.916 DEBUG akka://ENSIME/user/ensime-main/project/scalac o.e.c.Analyzer - received handled message FullTypeCheckCompleteEvent in state startup 16:28:36.245 DEBUG None o.e.i.SearchService - committing index to disk... 16:28:36.486 DEBUG None o.e.i.SearchService - ...done committing index 16:28:36.489 DEBUG akka://ENSIME/user/ensime-main/project o.e.c.Project - created 229459 and removed 0 searchable rows
connecting on port: 55392
"isStarted", Array] 0: "isStarted" 1: Array 0: Object client: Client destroy: () dotEnsime: Object isSourceOf: (path) rootDir: "/Users/magnus/Documents/Programmering/Magnusart/akka-persistence-cassandra/project" statusbarView: StatusbarView typechecking: Object addScalaNotes: (msg) clearScalaNotes: () destroy: () __proto__: Object __proto__: Object length: 1 __proto__: Array length: 2 __proto__: Array
indexingbridge-RELEASE731.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/lib/tools.jar -Densime.config=/Users/magnus/Documents/Programmering/Magnusart/akka-persistence-cassandra/project/.ensime -Densime.protocol=jerk org.ensime.server.Server ensime-startup.coffee:87 Seen: /Users/magnus/Documents/Programmering/Magnusart/akka-persistence-cassandra/project/.ensime_cache/http ensime-startup.coffee:82 starting watching for: /Users/magnus/Documents/Programmering/Magnusart/akka-persistence-cassandra/project/.ensime_cache/port ensime-startup.coffee:87 Seen: /Users/magnus/Documents/Programmering/Magnusart/akka-persistence-cassandra/project/.ensime_cache/port ensime-startup.coffee:90 All files seen. Starting client client.coffee:44 connecting on port: 55476 ensime.coffee:157 ["changed from ", Object, " to ", Object] client.coffee:46 client connected ensime.coffee:157 ["changed from ", Object, " to ", undefined]
16:56:07.981 ERROR akka://ENSIME/user/ensime-main/tcp-server/con1 o.e.s.t.TCPConnectionActor - Error seen during message processing, closing client connection java.lang.StackOverflowError: null at org.ensime.jerk.JerkConversions$fresh$macro$502$1.inst$macro$499$lzycompute(JerkFormats.scala:46) ~[jerky_2.11.jar:0.9.10-SNAPSHOT] at org.ensime.jerk.JerkConversions$fresh$macro$502$1.inst$macro$499(JerkFormats.scala:46) ~[jerky_2.11.jar:0.9.10-SNAPSHOT] at org.ensime.jerk.JerkConversions$fresh$macro$502$1.inst$macro$499$lzycompute(JerkFormats.scala:46) ~[jerky_2.11.jar:0.9.10-SNAPSHOT] goes one for about 1000 lines
Ensime server error event: Error: read ECONNRESET
Oh, @magnusart . You are running ensime on your meta project. The sbt build project, not the project itself.
watching for: /Users/magnus/Documents/Programmering/Magnusart/akka-persistence-cassandra/project/.ensime_cache/port
And then you move to a ”normal” scala file of which you are not running any ensime instance, which is logged as ”switching from object to undefined” and nothing is shown.
I got a feature request to auto-start without selecting .ensime IFF there is only one that isn’t already started. But I think this might be confusing sometimes.
gen-ensime-projectbut the normal
gen-ensimein the root. It was not super clear I realized. That I was trying out different scenarios.
/Users/magnus/Documents/Programmering/Magnusart/akka-persistence-cassandra/project/.ensime_cache/portIs the port file of an ensime running for your meta project
/Users/magnus/Documents/Programmering/Magnusart/akka-persistence-cassandra/.ensime_cache/portshould be your actual non-meta project.