[ANN] dont-give-up 0.1.0: Common Lisp style restarts in Clojure

Hey! Last week I sent an email announcing some code that I've been working on to bring Common Lisp style restarts to Clojure. I just released the first version! You can see it at https://github.com/czan/dont-give-up. More interestingly, though, I also have a working CIDER interface

Re: [ANN] dont-give-up: Common Lisp style restarts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This is really interesting thing. Checking it out. - -- [ stardiviner ] don't need to convince with trends. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3 --

[ANN] dont-give-up: Common Lisp style restarts

Hey! I've been playing around a little bit with Common Lisp lately, and I've found the interactive restarts to be pretty amazing. So, I've implemented something similar to them in Clojure/Cider! https://github.com/czan/dont-give-up It has support for programmatic res

Re: Stuart Sierra's Component: retries & restarts in production

g >> the component stack, I have some macros that wrap up exception handling, >> retries, and component stack restarts. >> >> So >> >> (with-rmq-publisher! [channel component-system] >> ... do my stuff ...) >> >> The body of the macro ("...

[ANN] trapperkeeper 1.3.0 - with support for restarts via HUP

Today we released puppetlabs/trapperkeeper v1.3.0 to clojars. Trapperkeeper[1] is a Clojure framework for hosting long-running applications and services. You can think of it as a sort of "binder" for Ring applications and other modular bits of Clojure code. The major change in the release is supp

Re: Stuart Sierra's Component: retries & restarts in production

s that require restarting > the component stack, I have some macros that wrap up exception handling, > retries, and component stack restarts. > > So > > (with-rmq-publisher! [channel component-system] > ... do my stuff ...) > > The body of the macro ("... do my st

Re: Stuart Sierra's Component: retries & restarts in production

On Thursday, September 3, 2015 at 9:15:54 AM UTC-4, Andy- wrote: > > Only to answer the "retry on error" part of you question: You might like > hara/event: > http://docs.caudate.me/hara/hara-event.html > Thanks for the tip! I've been meaning to check out hara anyway. If I end up using it I'll p

Re: Stuart Sierra's Component: retries & restarts in production

On 3 September 2015 at 00:03, wrote: > > The HTTP connection may be closed at any time by the server; if that > happens, the app should persistently attempt to reconnect using an > exponential back-off pattern. In addition, if the app goes thirty seconds > without receiving any data, it should clo

Re: Stuart Sierra's Component: retries & restarts in production

I just found the other resources from the Component wiki —it may be that something linked from there addresses exactly my situation. On Wednesday, September 2, 2015 at 8:44:07 PM UTC-4, jo...@signafire.com wrote: > > TLDR: how do you use

Re: Stuart Sierra's Component: retries & restarts in production

We make sure the components we build know how to restart themselves. This avoids the use of start/stop. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are

Re: Stuart Sierra's Component: retries & restarts in production

sure that I can deal with the exceptions that require restarting > the component stack, I have some macros that wrap up exception handling, > retries, and component stack restarts. > > So > > (with-rmq-publisher! [channel component-system] > ... do my stuff ...) > > The body

Re: Stuart Sierra's Component: retries & restarts in production

tions that require restarting the component stack, I have some macros that wrap up exception handling, retries, and component stack restarts. So (with-rmq-publisher! [channel component-system] ... do my stuff ...) The body of the macro ("... do my stuff ...") is turned into a funct

Re: Stuart Sierra's Component: retries & restarts in production

Only to answer the "retry on error" part of you question: You might like hara/event: http://docs.caudate.me/hara/hara-event.html HTH On Wednesday, September 2, 2015 at 8:44:07 PM UTC-4, jo...@signafire.com wrote: > > TLDR: how do you use Component when the application logic involves > retrying

Re: Stuart Sierra's Component: retries & restarts in production

Another way I can think of decomposing this is to buffer/queue communication between your two components, i.e a core.async channel. This will decouple the two components allowing your MessageQueue to manage it's own reconnection. Interesting question about whether `start` calling `stop` is blasphe

Stuart Sierra's Component: retries & restarts in production

TLDR: how do you use Component when the application logic involves retrying failed components? Background: I'm writing an app that consumes events from a streaming HTTP connection and writes those events to a message queue (see Code Illustration #1). It seems like that could be captured easily

Re: restarts

l (explode-on-invalid-entries!) )) Just let parse-log-entry return whether the entry was ok or not. So we can handle it outside. Might just return nil on invalid entries, but that loses information. Avoid Exceptions whereever possible. But again, I know nothing about CL so it might

Re: restarts

On Thursday, June 19, 2014 11:05:07 PM UTC+2, Thomas Heller wrote: > > Excuse my ignorance of not knowing anything about CL and restarts but I > needed something like retry a while back. > Restarts in CL are a different beast. Take a look at e.g. http://www.gigamonkeys.com

Re: restarts

Excuse my ignorance of not knowing anything about CL and restarts but I needed something like retry a while back. I started with something like this (defn do-something-that-might-fail [] (let [v (rand)] (prn [:v v]) (when (> v 0.1) (throw (ex-info "boom" {})))

Re: restarts

You may be interested in ribol: https://github.com/zcaudate/ribol http://docs.caudate.me/ribol/ I've not had a chance to play with it myself. On Thursday, 19 June 2014 17:25:04 UTC+1, Christopher Howard wrote: > > Does Clojure have restarts or continuable-errors like in CL? Or

restarts

Does Clojure have restarts or continuable-errors like in CL? Or something similiar? If not, is that something that could be implemented some how? -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email

Re: [ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

This is fantastic, Chris. Many thanks! ~BG On Tue, Oct 1, 2013 at 12:49 PM, Chris Zheng wrote: > Dima and BG, > > A new version is up with implementation details - > http://z.caudate.me/ribol/#implementation > > as well as the requested stacktrace … although I called it :origin instead > of :stac

Re: [ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

Dima and BG, A new version is up with implementation details - http://z.caudate.me/ribol/#implementation as well as the requested stacktrace … although I called it :origin instead of :stacktrace. - http://z.caudate.me/ribol/#raise-on Chris -- -- You received this message because you are sub

Re: [ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

t;> >> Version 0.3.1 has the following updates: >> >> >> >> The `finally` clause is supported on `manage` - >> >> http://z.caudate.me/ribol/#finally as well as all the hook forms - >> >> http://z.caudate.me/ribol/#h

Re: [ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

t;> `raise-on` and `raise-on-all` have been updated to work better with > thrown > >> clojure.lang.ExceptionInfo objects > >> > >> I've also put in a section on how code can be reused using restarts - > >> http://z.caudate.me/ribol/#unlucky-numbers > &g

Re: [ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

The `finally` clause is supported on `manage` - >> http://z.caudate.me/ribol/#finally as well as all the hook forms - >> http://z.caudate.me/ribol/#hooks >> >> `raise-on` and `raise-on-all` have been updated to work better with thrown >> clojure.lang.Except

Re: [ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

gt; clojure.lang.ExceptionInfo objects > > I've also put in a section on how code can be reused using restarts - > http://z.caudate.me/ribol/#unlucky-numbers > > -- > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group

[ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

` have been updated to work better with thrown clojure.lang.ExceptionInfo objects I've also put in a section on how code can be reused using restarts - http://z.caudate.me/ribol/#unlucky-numbers -- -- You received this message because you are subscribed to the Google Groups "Clojure"

Fast REPL restarts Re: Smarter code reloading with tools.namespace 0.2.0

REPL restarts are slow and costly, but the freshness they provide is obviously so valuable, too. Has anyone experimented with something like JRebel or some alternative to provide super-fast like fraction of a section REPL restarts? On Fri, Oct 5, 2012 at 8:56 AM, Stuart Sierra wrote

Re: HOWTO: Compojure Development without Web Server Restarts using VimClojure

Hi, Cool. Thank you for your report! Just some notes. On Dec 2, 3:10 am, Gilbert wrote: > - vimclojure offers a number of features, but the documentation is > hidden in a text file inside ~/.vim/doc/clojure.txt (you can also read > it here:  http://bitbucket.org/kotarak/vimclojure/src/tip/doc/c

HOWTO: Compojure Development without Web Server Restarts using VimClojure

I figured this out recently; hopefully this is helpful to others. 1. Install VimClojure http://kotka.de/projects/clojure/vimclojure.html - vimclojure offers a number of features, but the documentation is hidden in a text file inside ~/.vim/doc/clojure.txt (you can also read it here: http://bitbu