betfair/cougar issues and pull requests

#106 - [SECURITY] Use HTTPS to resolve dependencies in Gradle Build

Pull Request - State: open - Opened by JLLeitschuh over 2 years ago

#106 - [SECURITY] Use HTTPS to resolve dependencies in Gradle Build

Pull Request - State: open - Opened by JLLeitschuh over 2 years ago

#105 - [SECURITY] Fix Partial Path Traversal Vulnerability

Pull Request - State: open - Opened by JLLeitschuh over 2 years ago

#104 - [SECURITY] Use HTTPS to resolve dependencies in Maven Build

Pull Request - State: open - Opened by JLLeitschuh about 5 years ago

#104 - [SECURITY] Use HTTPS to resolve dependencies in Maven Build

Pull Request - State: open - Opened by JLLeitschuh about 5 years ago

#104 - [SECURITY] Use HTTPS to resolve dependencies in Maven Build

Pull Request - State: open - Opened by JLLeitschuh about 5 years ago

#103 - Fix #102 - Split Zipkin code into multiple maven modules.

Pull Request - State: closed - Opened by andredasilvapinto almost 9 years ago - 5 comments

#102 - Cleanup zipkin transport dependencies

Issue - State: open - Opened by eswdd over 9 years ago - 3 comments

#102 - Cleanup zipkin transport dependencies

Issue - State: open - Opened by eswdd over 9 years ago - 3 comments

#101 - Throw exception if try to construct service exception with null cause

Issue - State: closed - Opened by eswdd over 9 years ago
Labels: S

#101 - Throw exception if try to construct service exception with null cause

Issue - State: closed - Opened by eswdd over 9 years ago
Labels: S

#100 - Property value output on start up is rendered as {2} always (3.2)

Issue - State: closed - Opened by eswdd over 9 years ago

#100 - Property value output on start up is rendered as {2} always (3.2)

Issue - State: closed - Opened by eswdd over 9 years ago

#100 - Property value output on start up is rendered as {2} always (3.2)

Issue - State: closed - Opened by eswdd over 9 years ago

#99 - Property value output on start up is rendered as {2} always

Issue - State: closed - Opened by richardqd almost 10 years ago - 2 comments

#99 - Property value output on start up is rendered as {2} always

Issue - State: closed - Opened by richardqd almost 10 years ago - 2 comments

#99 - Property value output on start up is rendered as {2} always

Issue - State: closed - Opened by richardqd almost 10 years ago - 2 comments

#99 - Property value output on start up is rendered as {2} always

Issue - State: closed - Opened by richardqd almost 10 years ago - 2 comments

#98 - Implement Zipkin Support #74

Pull Request - State: closed - Opened by HugoMFernandes almost 10 years ago - 12 comments
Labels: accepted

#98 - Implement Zipkin Support #74

Pull Request - State: closed - Opened by HugoMFernandes almost 10 years ago - 12 comments
Labels: accepted

#98 - Implement Zipkin Support #74

Pull Request - State: closed - Opened by HugoMFernandes almost 10 years ago - 12 comments
Labels: accepted

#97 - Permit support for message parameter in exception idd definition

Issue - State: closed - Opened by richardqd almost 10 years ago

#97 - Permit support for message parameter in exception idd definition

Issue - State: closed - Opened by richardqd almost 10 years ago

#96 - Deprecate dataframe now we have cors

Issue - State: closed - Opened by eswdd about 10 years ago - 3 comments
Labels: invalid, wontfix, doco

#96 - Deprecate dataframe now we have cors

Issue - State: closed - Opened by eswdd about 10 years ago - 3 comments
Labels: invalid, wontfix, doco

#96 - Deprecate dataframe now we have cors

Issue - State: closed - Opened by eswdd about 10 years ago - 3 comments
Labels: invalid, wontfix, doco

#96 - Deprecate dataframe now we have cors

Issue - State: closed - Opened by eswdd about 10 years ago - 3 comments
Labels: invalid, wontfix, doco

#96 - Deprecate dataframe now we have cors

Issue - State: closed - Opened by eswdd about 10 years ago - 3 comments
Labels: invalid, wontfix, doco

#96 - Deprecate dataframe now we have cors

Issue - State: closed - Opened by eswdd about 10 years ago - 3 comments
Labels: invalid, wontfix, doco

#96 - Deprecate dataframe now we have cors

Issue - State: closed - Opened by eswdd about 10 years ago - 3 comments
Labels: invalid, wontfix, doco

#95 - Upgrade Jetty to >= 9.1

Issue - State: closed - Opened by andredasilvapinto about 10 years ago - 7 comments
Labels: enhancement, accepted

#95 - Upgrade Jetty to >= 9.1

Issue - State: closed - Opened by andredasilvapinto about 10 years ago - 7 comments
Labels: enhancement, accepted

#95 - Upgrade Jetty to >= 9.1

Issue - State: closed - Opened by andredasilvapinto about 10 years ago - 7 comments
Labels: enhancement, accepted

#95 - Upgrade Jetty to >= 9.1

Issue - State: closed - Opened by andredasilvapinto about 10 years ago - 7 comments
Labels: enhancement, accepted

#95 - Upgrade Jetty to >= 9.1

Issue - State: closed - Opened by andredasilvapinto about 10 years ago - 7 comments
Labels: enhancement, accepted

#95 - Upgrade Jetty to >= 9.1

Issue - State: closed - Opened by andredasilvapinto about 10 years ago - 7 comments
Labels: enhancement, accepted

#94 - InterceptingExecutableWrapper bug introduced Feb 2014

Issue - State: open - Opened by eswdd about 10 years ago

#94 - InterceptingExecutableWrapper bug introduced Feb 2014

Issue - State: open - Opened by eswdd about 10 years ago

#94 - InterceptingExecutableWrapper bug introduced Feb 2014

Issue - State: open - Opened by eswdd about 10 years ago

#93 - Socket protocol compatibility testing

Issue - State: open - Opened by eswdd about 10 years ago - 4 comments
Labels: in progress

#93 - Socket protocol compatibility testing

Issue - State: open - Opened by eswdd about 10 years ago - 4 comments
Labels: in progress

#93 - Socket protocol compatibility testing

Issue - State: open - Opened by eswdd about 10 years ago - 4 comments
Labels: in progress

#92 - Consider using netty

Issue - State: open - Opened by eswdd about 10 years ago - 2 comments

#92 - Consider using netty

Issue - State: open - Opened by eswdd about 10 years ago - 2 comments

#92 - Consider using netty

Issue - State: open - Opened by eswdd about 10 years ago - 2 comments

#91 - Bug in the generated client code regarding TimeConstraints - TRUNK fix

Issue - State: closed - Opened by eswdd about 10 years ago
Labels: bug, accepted

#91 - Bug in the generated client code regarding TimeConstraints - TRUNK fix

Issue - State: closed - Opened by eswdd about 10 years ago
Labels: bug, accepted

#91 - Bug in the generated client code regarding TimeConstraints - TRUNK fix

Issue - State: closed - Opened by eswdd about 10 years ago
Labels: bug, accepted

#91 - Bug in the generated client code regarding TimeConstraints - TRUNK fix

Issue - State: closed - Opened by eswdd about 10 years ago
Labels: bug, accepted

#91 - Bug in the generated client code regarding TimeConstraints - TRUNK fix

Issue - State: closed - Opened by eswdd about 10 years ago
Labels: bug, accepted

#91 - Bug in the generated client code regarding TimeConstraints - TRUNK fix

Issue - State: closed - Opened by eswdd about 10 years ago
Labels: bug, accepted

#91 - Bug in the generated client code regarding TimeConstraints - TRUNK fix

Issue - State: closed - Opened by eswdd about 10 years ago
Labels: bug, accepted

#90 - Add json-rpc support to client

Issue - State: open - Opened by eswdd about 10 years ago

#90 - Add json-rpc support to client

Issue - State: open - Opened by eswdd about 10 years ago

#90 - Add json-rpc support to client

Issue - State: open - Opened by eswdd about 10 years ago

#90 - Add json-rpc support to client

Issue - State: open - Opened by eswdd about 10 years ago

#90 - Add json-rpc support to client

Issue - State: open - Opened by eswdd about 10 years ago

#90 - Add json-rpc support to client

Issue - State: open - Opened by eswdd about 10 years ago

#90 - Add json-rpc support to client

Issue - State: open - Opened by eswdd about 10 years ago

#90 - Add json-rpc support to client

Issue - State: open - Opened by eswdd about 10 years ago

#90 - Add json-rpc support to client

Issue - State: open - Opened by eswdd about 10 years ago

#90 - Add json-rpc support to client

Issue - State: open - Opened by eswdd about 10 years ago

#90 - Add json-rpc support to client

Issue - State: open - Opened by eswdd about 10 years ago

#90 - Add json-rpc support to client

Issue - State: open - Opened by eswdd about 10 years ago

#89 - Introducing CORS support.

Pull Request - State: closed - Opened by jorgemsrs over 10 years ago - 13 comments

#89 - Introducing CORS support.

Pull Request - State: closed - Opened by jorgemsrs over 10 years ago - 13 comments

#89 - Introducing CORS support.

Pull Request - State: closed - Opened by jorgemsrs over 10 years ago - 13 comments

#89 - Introducing CORS support.

Pull Request - State: closed - Opened by jorgemsrs over 10 years ago - 13 comments

#89 - Introducing CORS support.

Pull Request - State: closed - Opened by jorgemsrs over 10 years ago - 13 comments

#89 - Introducing CORS support.

Pull Request - State: closed - Opened by jorgemsrs over 10 years ago - 13 comments

#89 - Introducing CORS support.

Pull Request - State: closed - Opened by jorgemsrs over 10 years ago - 13 comments

#89 - Introducing CORS support.

Pull Request - State: closed - Opened by jorgemsrs over 10 years ago - 13 comments

#88 - New transport for Swagger Spec

Issue - State: closed - Opened by jorgemsrs over 10 years ago - 8 comments
Labels: enhancement, wontfix

#88 - New transport for Swagger Spec

Issue - State: closed - Opened by jorgemsrs over 10 years ago - 8 comments
Labels: enhancement, wontfix

#88 - New transport for Swagger Spec

Issue - State: closed - Opened by jorgemsrs over 10 years ago - 8 comments
Labels: enhancement, wontfix

#88 - New transport for Swagger Spec

Issue - State: closed - Opened by jorgemsrs over 10 years ago - 8 comments
Labels: enhancement, wontfix

#87 - CORS support

Issue - State: closed - Opened by jorgemsrs over 10 years ago - 6 comments
Labels: enhancement, security, accepted

#87 - CORS support

Issue - State: closed - Opened by jorgemsrs over 10 years ago - 6 comments
Labels: enhancement, security, accepted

#87 - CORS support

Issue - State: closed - Opened by jorgemsrs over 10 years ago - 6 comments
Labels: enhancement, security, accepted

#87 - CORS support

Issue - State: closed - Opened by jorgemsrs over 10 years ago - 6 comments
Labels: enhancement, security, accepted

#87 - CORS support

Issue - State: closed - Opened by jorgemsrs over 10 years ago - 6 comments
Labels: enhancement, security, accepted

#86 - The new asyncHttpReponseProcessorThreadPool should be exposed via JMX

Issue - State: closed - Opened by andredasilvapinto over 10 years ago - 1 comment
Labels: bug, accepted

#86 - The new asyncHttpReponseProcessorThreadPool should be exposed via JMX

Issue - State: closed - Opened by andredasilvapinto over 10 years ago - 1 comment
Labels: bug, accepted

#86 - The new asyncHttpReponseProcessorThreadPool should be exposed via JMX

Issue - State: closed - Opened by andredasilvapinto over 10 years ago - 1 comment
Labels: bug, accepted

#85 - #84 Fixing calculation of TimeConstraints based on timeouts for Async clients

Pull Request - State: closed - Opened by andredasilvapinto over 10 years ago - 7 comments

#85 - #84 Fixing calculation of TimeConstraints based on timeouts for Async clients

Pull Request - State: closed - Opened by andredasilvapinto over 10 years ago - 7 comments

#85 - #84 Fixing calculation of TimeConstraints based on timeouts for Async clients

Pull Request - State: closed - Opened by andredasilvapinto over 10 years ago - 7 comments

#85 - #84 Fixing calculation of TimeConstraints based on timeouts for Async clients

Pull Request - State: closed - Opened by andredasilvapinto over 10 years ago - 7 comments

#85 - #84 Fixing calculation of TimeConstraints based on timeouts for Async clients

Pull Request - State: closed - Opened by andredasilvapinto over 10 years ago - 7 comments

#85 - #84 Fixing calculation of TimeConstraints based on timeouts for Async clients

Pull Request - State: closed - Opened by andredasilvapinto over 10 years ago - 7 comments

#85 - #84 Fixing calculation of TimeConstraints based on timeouts for Async clients

Pull Request - State: closed - Opened by andredasilvapinto over 10 years ago - 7 comments

#85 - #84 Fixing calculation of TimeConstraints based on timeouts for Async clients

Pull Request - State: closed - Opened by andredasilvapinto over 10 years ago - 7 comments

#85 - #84 Fixing calculation of TimeConstraints based on timeouts for Async clients

Pull Request - State: closed - Opened by andredasilvapinto over 10 years ago - 7 comments

#85 - #84 Fixing calculation of TimeConstraints based on timeouts for Async clients

Pull Request - State: closed - Opened by andredasilvapinto over 10 years ago - 7 comments

#84 - Bug in the generated client code regarding TimeConstraints

Issue - State: closed - Opened by andredasilvapinto over 10 years ago - 2 comments
Labels: bug, accepted

#84 - Bug in the generated client code regarding TimeConstraints

Issue - State: closed - Opened by andredasilvapinto over 10 years ago - 2 comments
Labels: bug, accepted

#84 - Bug in the generated client code regarding TimeConstraints

Issue - State: closed - Opened by andredasilvapinto over 10 years ago - 2 comments
Labels: bug, accepted

#84 - Bug in the generated client code regarding TimeConstraints

Issue - State: closed - Opened by andredasilvapinto over 10 years ago - 2 comments
Labels: bug, accepted

#84 - Bug in the generated client code regarding TimeConstraints

Issue - State: closed - Opened by andredasilvapinto over 10 years ago - 2 comments
Labels: bug, accepted

#84 - Bug in the generated client code regarding TimeConstraints

Issue - State: closed - Opened by andredasilvapinto over 10 years ago - 2 comments
Labels: bug, accepted

GitHub / betfair/cougar issues and pull requests