dispatch/reboot issues and pull requests

#141 - Add Java 8 to Travis build for dispatch 0.11.3

Pull Request - State: closed - Opened by ashawley over 7 years ago - 4 comments

#141 - Add Java 8 to Travis build for dispatch 0.11.3

Pull Request - State: closed - Opened by ashawley over 7 years ago - 4 comments

#132 - Turn on Scala lint warnings

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#132 - Turn on Scala lint warnings

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#132 - Turn on Scala lint warnings

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#132 - Turn on Scala lint warnings

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#132 - Turn on Scala lint warnings

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#132 - Turn on Scala lint warnings

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#132 - Turn on Scala lint warnings

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#132 - Turn on Scala lint warnings

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#132 - Turn on Scala lint warnings

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#131 - Fix Travis by upgrading Scala and host addon

Pull Request - State: closed - Opened by ashawley almost 8 years ago - 3 comments

#122 - setUseProxyProperties does nothing

Issue - State: closed - Opened by henry0312 over 8 years ago - 1 comment

#122 - setUseProxyProperties does nothing

Issue - State: closed - Opened by henry0312 over 8 years ago - 1 comment

#122 - setUseProxyProperties does nothing

Issue - State: closed - Opened by henry0312 over 8 years ago - 1 comment

#122 - setUseProxyProperties does nothing

Issue - State: closed - Opened by henry0312 over 8 years ago - 1 comment

#122 - setUseProxyProperties does nothing

Issue - State: closed - Opened by henry0312 over 8 years ago - 1 comment

#122 - setUseProxyProperties does nothing

Issue - State: closed - Opened by henry0312 over 8 years ago - 1 comment

#122 - setUseProxyProperties does nothing

Issue - State: closed - Opened by henry0312 over 8 years ago - 1 comment

#122 - setUseProxyProperties does nothing

Issue - State: closed - Opened by henry0312 over 8 years ago - 1 comment

#122 - setUseProxyProperties does nothing

Issue - State: closed - Opened by henry0312 over 8 years ago - 1 comment

#122 - setUseProxyProperties does nothing

Issue - State: closed - Opened by henry0312 over 8 years ago - 1 comment

#122 - setUseProxyProperties does nothing

Issue - State: closed - Opened by henry0312 over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#121 - App hangs if Http.configure has been used

Issue - State: closed - Opened by vchekan over 8 years ago - 1 comment

#119 - as.File has File Descriptor leak

Issue - State: closed - Opened by seraphr almost 9 years ago - 3 comments
Labels: bug, 0.12-backport, 0.13-backport

#119 - as.File has File Descriptor leak

Issue - State: closed - Opened by seraphr almost 9 years ago - 3 comments
Labels: bug, 0.12-backport, 0.13-backport

#119 - as.File has File Descriptor leak

Issue - State: closed - Opened by seraphr almost 9 years ago - 3 comments
Labels: bug, 0.12-backport, 0.13-backport

#119 - as.File has File Descriptor leak

Issue - State: closed - Opened by seraphr almost 9 years ago - 3 comments
Labels: bug, 0.12-backport, 0.13-backport

#119 - as.File has File Descriptor leak

Issue - State: closed - Opened by seraphr almost 9 years ago - 3 comments
Labels: bug, 0.12-backport, 0.13-backport

#119 - as.File has File Descriptor leak

Issue - State: closed - Opened by seraphr almost 9 years ago - 3 comments
Labels: bug, 0.12-backport, 0.13-backport

#119 - as.File has File Descriptor leak

Issue - State: closed - Opened by seraphr almost 9 years ago - 3 comments
Labels: bug, 0.12-backport, 0.13-backport

#114 - Http.configure creates a new HTTP client but doesn't shutdown the old reference.

Issue - State: closed - Opened by damienlevin about 9 years ago - 2 comments

#114 - Http.configure creates a new HTTP client but doesn't shutdown the old reference.

Issue - State: closed - Opened by damienlevin about 9 years ago - 2 comments

#114 - Http.configure creates a new HTTP client but doesn't shutdown the old reference.

Issue - State: closed - Opened by damienlevin about 9 years ago - 2 comments

#114 - Http.configure creates a new HTTP client but doesn't shutdown the old reference.

Issue - State: closed - Opened by damienlevin about 9 years ago - 2 comments

#114 - Http.configure creates a new HTTP client but doesn't shutdown the old reference.

Issue - State: closed - Opened by damienlevin about 9 years ago - 2 comments

#114 - Http.configure creates a new HTTP client but doesn't shutdown the old reference.

Issue - State: closed - Opened by damienlevin about 9 years ago - 2 comments

#114 - Http.configure creates a new HTTP client but doesn't shutdown the old reference.

Issue - State: closed - Opened by damienlevin about 9 years ago - 2 comments

#114 - Http.configure creates a new HTTP client but doesn't shutdown the old reference.

Issue - State: closed - Opened by damienlevin about 9 years ago - 2 comments

#114 - Http.configure creates a new HTTP client but doesn't shutdown the old reference.

Issue - State: closed - Opened by damienlevin about 9 years ago - 2 comments

#114 - Http.configure creates a new HTTP client but doesn't shutdown the old reference.

Issue - State: closed - Opened by damienlevin about 9 years ago - 2 comments

#113 - Dispatch throws exceptions, Ning doesn't catch… neither does Netty!

Issue - State: closed - Opened by djspiewak about 9 years ago - 1 comment

#113 - Dispatch throws exceptions, Ning doesn't catch… neither does Netty!

Issue - State: closed - Opened by djspiewak about 9 years ago - 1 comment

#113 - Dispatch throws exceptions, Ning doesn't catch… neither does Netty!

Issue - State: closed - Opened by djspiewak about 9 years ago - 1 comment

#113 - Dispatch throws exceptions, Ning doesn't catch… neither does Netty!

Issue - State: closed - Opened by djspiewak about 9 years ago - 1 comment

#113 - Dispatch throws exceptions, Ning doesn't catch… neither does Netty!

Issue - State: closed - Opened by djspiewak about 9 years ago - 1 comment

#113 - Dispatch throws exceptions, Ning doesn't catch… neither does Netty!

Issue - State: closed - Opened by djspiewak about 9 years ago - 1 comment

#113 - Dispatch throws exceptions, Ning doesn't catch… neither does Netty!

Issue - State: closed - Opened by djspiewak about 9 years ago - 1 comment

#113 - Dispatch throws exceptions, Ning doesn't catch… neither does Netty!

Issue - State: closed - Opened by djspiewak about 9 years ago - 1 comment

#113 - Dispatch throws exceptions, Ning doesn't catch… neither does Netty!

Issue - State: closed - Opened by djspiewak about 9 years ago - 1 comment

#112 - Dispatch hogs the CPU after shutting down a custom configured `Http` instance

Issue - State: closed - Opened by maciej about 9 years ago - 1 comment

#112 - Dispatch hogs the CPU after shutting down a custom configured `Http` instance

Issue - State: closed - Opened by maciej about 9 years ago - 1 comment

#112 - Dispatch hogs the CPU after shutting down a custom configured `Http` instance

Issue - State: closed - Opened by maciej about 9 years ago - 1 comment

#112 - Dispatch hogs the CPU after shutting down a custom configured `Http` instance

Issue - State: closed - Opened by maciej about 9 years ago - 1 comment

#112 - Dispatch hogs the CPU after shutting down a custom configured `Http` instance

Issue - State: closed - Opened by maciej about 9 years ago - 1 comment

#112 - Dispatch hogs the CPU after shutting down a custom configured `Http` instance

Issue - State: closed - Opened by maciej about 9 years ago - 1 comment

#112 - Dispatch hogs the CPU after shutting down a custom configured `Http` instance

Issue - State: closed - Opened by maciej about 9 years ago - 1 comment

#112 - Dispatch hogs the CPU after shutting down a custom configured `Http` instance

Issue - State: closed - Opened by maciej about 9 years ago - 1 comment

#112 - Dispatch hogs the CPU after shutting down a custom configured `Http` instance

Issue - State: closed - Opened by maciej about 9 years ago - 1 comment

#112 - Dispatch hogs the CPU after shutting down a custom configured `Http` instance

Issue - State: closed - Opened by maciej about 9 years ago - 1 comment

#112 - Dispatch hogs the CPU after shutting down a custom configured `Http` instance

Issue - State: closed - Opened by maciej about 9 years ago - 1 comment

#112 - Dispatch hogs the CPU after shutting down a custom configured `Http` instance

Issue - State: closed - Opened by maciej about 9 years ago - 1 comment

#111 - Having to unwrap exceptions from ExecutionException

Issue - State: open - Opened by maciej about 9 years ago - 2 comments
Labels: improvement

#111 - Having to unwrap exceptions from ExecutionException

Issue - State: open - Opened by maciej about 9 years ago - 2 comments
Labels: improvement

#111 - Having to unwrap exceptions from ExecutionException

Issue - State: open - Opened by maciej about 9 years ago - 2 comments
Labels: improvement

#111 - Having to unwrap exceptions from ExecutionException

Issue - State: open - Opened by maciej about 9 years ago - 2 comments
Labels: improvement

#111 - Having to unwrap exceptions from ExecutionException

Issue - State: open - Opened by maciej about 9 years ago - 2 comments
Labels: improvement

#111 - Having to unwrap exceptions from ExecutionException

Issue - State: open - Opened by maciej about 9 years ago - 2 comments
Labels: improvement

#111 - Having to unwrap exceptions from ExecutionException

Issue - State: open - Opened by maciej about 9 years ago - 2 comments
Labels: improvement

#111 - Having to unwrap exceptions from ExecutionException

Issue - State: open - Opened by maciej about 9 years ago - 2 comments
Labels: improvement

GitHub / dispatch/reboot issues and pull requests