search

dgrnbrg / vim-redl

A better Vim integration story for Clojure
106 stars 8 forks source link

Critical timeout-repl has been lost #11

Closed noahlz closed 11 years ago

noahlz commented 11 years ago

I'm frequently seeing the message Critical timeout-repl has been lost. 

user=> (require '[datomic.api :as d])
Critical timeout-repl has been lost
user=> (doc d/db)
-------------------------
datomic.api/db
([connection])
Retrieves a value of the database for reading.
nil
user=>

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 4 2012 04:22:36)
Clojure 1.5.1 Leiningen 2.1.2 on Java 1.6.0_41 Java HotSpot(TM) 64-Bit Server VM

dgrnbrg commented 11 years ago

This occurs when >10s elapses when you run a command. Is this the case for you?

The idea here is to unblock the single-threaded vim process.

On Tue, May 7, 2013 at 10:54 PM, Noah Zucker notifications@github.comwrote:

I'm frequently seeing the message Critical timeout-repl has been lost.

user=> (require '[datomic.api :as d]) Critical timeout-repl has been lost

user=> (doc d/db)

datomic.api/db ([connection]) Retrieves a value of the database for reading. nil user=>

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 4 2012 04:22:36)

Clojure 1.5.1 Leiningen 2.1.2 on Java 1.6.0_41 Java HotSpot(TM) 64-Bit Server VM

— Reply to this email directly or view it on GitHubhttps://github.com/dgrnbrg/vim-redl/issues/11 .

noahlz commented 11 years ago

Yes, but in my case I'm seeing it with commands that typically shouldn't take 10 seconds (as in the example). It's difficult to reproduce consistently.

How can I get more information about what's going on behind the scenes? I am a vimscript novice.

Perhaps I can set it to allow commands > 10 s?

dgrnbrg commented 11 years ago

I am not exactly sure, but it's a good thing that I organize the Clojure NYC User's Group, so we can deep dive this on Wednesday :)

On Wed, May 8, 2013 at 11:08 AM, Noah Zucker notifications@github.comwrote:

Yes, but in my case commands that typically shouldn't take 10 seconds (as in the example) do. It's difficult to reproduce consistently.

How can I get more information about what's going on behind the scenes? I am a vimscript novice.

— Reply to this email directly or view it on GitHubhttps://github.com/dgrnbrg/vim-redl/issues/11#issuecomment-17611904 .

noahlz commented 11 years ago

Cool - in fact, I offered to "show and tell" (as opposed to demo) my Clojure vim set up at the upcoming meetup, with the goal of getting feedback /discussing issues I've encountered (like this one). On May 12, 2013 12:20 PM, "dgrnbrg" notifications@github.com wrote:

I am not exactly sure, but it's a good thing that I organize the Clojure NYC User's Group, so we can deep dive this on Wednesday :)

On Wed, May 8, 2013 at 11:08 AM, Noah Zucker notifications@github.comwrote:

Yes, but in my case commands that typically shouldn't take 10 seconds (as in the example) do. It's difficult to reproduce consistently.

How can I get more information about what's going on behind the scenes? I am a vimscript novice.

— Reply to this email directly or view it on GitHub< https://github.com/dgrnbrg/vim-redl/issues/11#issuecomment-17611904> .

— Reply to this email directly or view it on GitHubhttps://github.com/dgrnbrg/vim-redl/issues/11#issuecomment-17780463 .

dgrnbrg commented 11 years ago

I'd be happy to jump up and demonstrate how it works during the meetup, and to look at your issue more closely afterwards.

On Sun, May 12, 2013 at 1:15 PM, Noah Zucker notifications@github.comwrote:

Cool - in fact, I offered to "show and tell" (as opposed to demo) my Clojure vim set up at the upcoming meetup, with the goal of getting feedback /discussing issues I've encountered (like this one). On May 12, 2013 12:20 PM, "dgrnbrg" notifications@github.com wrote:

I am not exactly sure, but it's a good thing that I organize the Clojure NYC User's Group, so we can deep dive this on Wednesday :)

On Wed, May 8, 2013 at 11:08 AM, Noah Zucker notifications@github.comwrote:

Yes, but in my case commands that typically shouldn't take 10 seconds (as in the example) do. It's difficult to reproduce consistently.

How can I get more information about what's going on behind the scenes? I am a vimscript novice.

— Reply to this email directly or view it on GitHub< https://github.com/dgrnbrg/vim-redl/issues/11#issuecomment-17611904> .

— Reply to this email directly or view it on GitHub< https://github.com/dgrnbrg/vim-redl/issues/11#issuecomment-17780463> .

— Reply to this email directly or view it on GitHubhttps://github.com/dgrnbrg/vim-redl/issues/11#issuecomment-17781347 .

noahlz commented 11 years ago

Awesome, thanks! On May 12, 2013 1:51 PM, "dgrnbrg" notifications@github.com wrote:

I'd be happy to jump up and demonstrate how it works during the meetup, and to look at your issue more closely afterwards.

On Sun, May 12, 2013 at 1:15 PM, Noah Zucker notifications@github.comwrote:

Cool - in fact, I offered to "show and tell" (as opposed to demo) my Clojure vim set up at the upcoming meetup, with the goal of getting feedback /discussing issues I've encountered (like this one). On May 12, 2013 12:20 PM, "dgrnbrg" notifications@github.com wrote:

I am not exactly sure, but it's a good thing that I organize the Clojure NYC User's Group, so we can deep dive this on Wednesday :)

On Wed, May 8, 2013 at 11:08 AM, Noah Zucker notifications@github.comwrote:

Yes, but in my case commands that typically shouldn't take 10 seconds (as in the example) do. It's difficult to reproduce consistently.

How can I get more information about what's going on behind the scenes? I am a vimscript novice.

— Reply to this email directly or view it on GitHub< https://github.com/dgrnbrg/vim-redl/issues/11#issuecomment-17611904> .

— Reply to this email directly or view it on GitHub< https://github.com/dgrnbrg/vim-redl/issues/11#issuecomment-17780463> .

— Reply to this email directly or view it on GitHub< https://github.com/dgrnbrg/vim-redl/issues/11#issuecomment-17781347> .

— Reply to this email directly or view it on GitHubhttps://github.com/dgrnbrg/vim-redl/issues/11#issuecomment-17781993 .

noahlz commented 11 years ago

Hmm, still seeing this quite a bit. Granted, I have a tehsuck laptop.

user=> (defonce server (run-jetty #'app {:port 8080 :configurator (fn [server] (println server))}))
Critical timeout-repl has been lost
user=> server
Critical timeout-repl has been lost
user=> server
Critical timeout-repl has  been lost

How do I lengthen the timeout?

dgrnbrg commented 11 years ago

In the redl project, there's now a way to set the timeout yourself. That feature solves the issue as best as I can with the current design of vim-redl.

noahlz commented 11 years ago

:thumbsup: