Issues
- 4
- 1
parameterize the executor
#57 opened by jasonjckn - 1
- 1
periodic-seq example and DST changes
#54 opened by terjesb - 1
Error in the doc-string?
#55 opened by 2food - 1
multiple chime-at calls
#53 opened by awb99 - 17
New feature: request upcoming chimes
#30 opened by pmonks - 1
- 1
Long running tasks
#49 opened by ilevd - 1
On-finished weird behaviours
#51 opened by AndreaCrotti - 1
chime-at API changes
#50 opened by AndreaCrotti - 4
thread factory name is always "chime-"
#33 opened by orestis - 2
Examples assume Dates instead of Instants?
#47 opened by werenike - 1
Drop times that have already passed
#48 opened by werenike - 3
Error running scheduled fn java.lang.NullPointerException: Cannot invoke "String.length()" because "s" is null
#46 opened by PlumpMath - 2
- 42
- 4
periodic-seq NullPointerException
#45 opened by elamje - 5
Dynamic bindings not conveyed
#43 opened by jimpil - 3
Core.async integration doc-string
#44 opened by jarohen - 1
Expose :thread-factory option
#41 opened by jimpil - 1
Dependency to clj-time unnecessary
#40 opened by dpiliouras - 3
Thread names don't include numbers
#38 opened by pmonks - 1
- 2
Multiple invocations of `on-finished`
#36 opened by dazld - 2
- 4
- 7
- 2
- 4
Support for times already past in `chime-at`
#19 opened by luminusian - 1
Replace Joda Time with JDK's java.time
#26 opened by holyjak - 2
:error-handler does not seem to be called
#22 opened by tuscland - 4
- 2
chime-at calls callback after schedule is cancelled if a previous callback overruns
#16 opened by dkharlan - 1
- 3
Breaks on newer core.async version
#15 opened by akiroz - 4
Non determenistic behavior
#13 opened by favetelinguis - 2
- 5
- 2
- 2
- 3
Use of deprecated clj-time function
#2 opened by jphackworth