Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / jupnp/jupnp issues and pull requests

#114 - provided capabilities for services

Issue - State: closed - Opened by maggu2810 almost 6 years ago

#114 - provided capabilities for services

Issue - State: closed - Opened by maggu2810 almost 6 years ago

#114 - provided capabilities for services

Issue - State: closed - Opened by maggu2810 almost 6 years ago

#114 - provided capabilities for services

Issue - State: closed - Opened by maggu2810 almost 6 years ago

#113 - Increased upper limit for thread count of Jetty client

Pull Request - State: closed - Opened by kaikreuzer almost 6 years ago

#113 - Increased upper limit for thread count of Jetty client

Pull Request - State: closed - Opened by kaikreuzer almost 6 years ago

#113 - Increased upper limit for thread count of Jetty client

Pull Request - State: closed - Opened by kaikreuzer almost 6 years ago

#113 - Increased upper limit for thread count of Jetty client

Pull Request - State: closed - Opened by kaikreuzer almost 6 years ago

#111 - Clean up tool.jar dependency

Pull Request - State: closed - Opened by htreu about 6 years ago

#111 - Clean up tool.jar dependency

Pull Request - State: closed - Opened by htreu about 6 years ago

#111 - Clean up tool.jar dependency

Pull Request - State: closed - Opened by htreu about 6 years ago

#111 - Clean up tool.jar dependency

Pull Request - State: closed - Opened by htreu about 6 years ago

#110 - Java 11 compatibility

Issue - State: closed - Opened by htreu about 6 years ago

#110 - Java 11 compatibility

Issue - State: closed - Opened by htreu about 6 years ago

#110 - Java 11 compatibility

Issue - State: closed - Opened by htreu about 6 years ago

#110 - Java 11 compatibility

Issue - State: closed - Opened by htreu about 6 years ago

#109 - NPE if https scheme is used by a UPnP device in the network

Issue - State: closed - Opened by kaikreuzer about 6 years ago - 3 comments

#109 - NPE if https scheme is used by a UPnP device in the network

Issue - State: closed - Opened by kaikreuzer about 6 years ago - 3 comments

#109 - NPE if https scheme is used by a UPnP device in the network

Issue - State: closed - Opened by kaikreuzer about 6 years ago - 3 comments

#109 - NPE if https scheme is used by a UPnP device in the network

Issue - State: closed - Opened by kaikreuzer about 6 years ago - 3 comments

#109 - NPE if https scheme is used by a UPnP device in the network

Issue - State: closed - Opened by kaikreuzer about 6 years ago - 3 comments

#107 - Cannot start service for Android runtime

Issue - State: open - Opened by eakteam about 6 years ago - 1 comment

#107 - Cannot start service for Android runtime

Issue - State: open - Opened by eakteam about 6 years ago - 1 comment

#107 - Cannot start service for Android runtime

Issue - State: open - Opened by eakteam about 6 years ago - 1 comment

#107 - Cannot start service for Android runtime

Issue - State: open - Opened by eakteam about 6 years ago - 1 comment

#107 - Cannot start service for Android runtime

Issue - State: open - Opened by eakteam about 6 years ago - 1 comment

#107 - Cannot start service for Android runtime

Issue - State: closed - Opened by eakteam about 6 years ago - 2 comments

#106 - Improve JettyStreamClient logging

Pull Request - State: closed - Opened by velichkos over 6 years ago

#106 - Improve JettyStreamClient logging

Pull Request - State: closed - Opened by velichkos over 6 years ago

#106 - Improve JettyStreamClient logging

Pull Request - State: closed - Opened by velichkos over 6 years ago

#106 - Improve JettyStreamClient logging

Pull Request - State: closed - Opened by velichkos over 6 years ago

#106 - Improve JettyStreamClient logging

Pull Request - State: closed - Opened by velichkos over 6 years ago

#106 - Improve JettyStreamClient logging

Pull Request - State: closed - Opened by velichkos over 6 years ago

#105 - Reduce number of Jetty threads

Pull Request - State: closed - Opened by velichkos over 6 years ago - 1 comment

#105 - Reduce number of Jetty threads

Pull Request - State: closed - Opened by velichkos over 6 years ago - 1 comment

#105 - Reduce number of Jetty threads

Pull Request - State: closed - Opened by velichkos over 6 years ago - 1 comment

#105 - Reduce number of Jetty threads

Pull Request - State: closed - Opened by velichkos over 6 years ago - 1 comment

#105 - Reduce number of Jetty threads

Pull Request - State: closed - Opened by velichkos over 6 years ago - 1 comment

#105 - Reduce number of Jetty threads

Pull Request - State: closed - Opened by velichkos over 6 years ago - 1 comment

#104 - Optimize device information retrieval error handling

Pull Request - State: closed - Opened by velichkos over 6 years ago

#104 - Optimize device information retrieval error handling

Pull Request - State: closed - Opened by velichkos over 6 years ago

#104 - Optimize device information retrieval error handling

Pull Request - State: closed - Opened by velichkos over 6 years ago

#103 - also catch IAEs from servlet registration

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#103 - also catch IAEs from servlet registration

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#103 - also catch IAEs from servlet registration

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#103 - also catch IAEs from servlet registration

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#103 - also catch IAEs from servlet registration

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#103 - also catch IAEs from servlet registration

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#103 - also catch IAEs from servlet registration

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#102 - make code null safe on shutdown

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#102 - make code null safe on shutdown

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#102 - make code null safe on shutdown

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#102 - make code null safe on shutdown

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#102 - make code null safe on shutdown

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#102 - make code null safe on shutdown

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#101 - make code null safe

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#101 - make code null safe

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#101 - make code null safe

Pull Request - State: closed - Opened by kaikreuzer over 6 years ago

#100 - allow access to sun packages

Pull Request - State: closed - Opened by sjsf over 6 years ago

#100 - allow access to sun packages

Pull Request - State: closed - Opened by sjsf over 6 years ago

#100 - allow access to sun packages

Pull Request - State: closed - Opened by sjsf over 6 years ago

#100 - allow access to sun packages

Pull Request - State: closed - Opened by sjsf over 6 years ago

#100 - allow access to sun packages

Pull Request - State: closed - Opened by sjsf over 6 years ago

#100 - allow access to sun packages

Pull Request - State: closed - Opened by sjsf over 6 years ago

#100 - allow access to sun packages

Pull Request - State: closed - Opened by sjsf over 6 years ago

#99 - Logs flooded with warnings about wrong device type string

Issue - State: closed - Opened by JochenHiller over 6 years ago - 2 comments

#99 - Logs flooded with warnings about wrong device type string

Issue - State: closed - Opened by JochenHiller over 6 years ago - 2 comments

#99 - Logs flooded with warnings about wrong device type string

Issue - State: closed - Opened by JochenHiller over 6 years ago - 2 comments

#99 - Logs flooded with warnings about wrong device type string

Issue - State: closed - Opened by JochenHiller over 6 years ago - 2 comments

#98 - Ignore bad value for state variable when handling a GENA event

Pull Request - State: closed - Opened by lolodomo over 6 years ago - 2 comments

#98 - Ignore bad value for state variable when handling a GENA event

Pull Request - State: closed - Opened by lolodomo over 6 years ago - 2 comments

#98 - Ignore bad value for state variable when handling a GENA event

Pull Request - State: closed - Opened by lolodomo over 6 years ago - 2 comments

#98 - Ignore bad value for state variable when handling a GENA event

Pull Request - State: closed - Opened by lolodomo over 6 years ago - 2 comments

#98 - Ignore bad value for state variable when handling a GENA event

Pull Request - State: closed - Opened by lolodomo over 6 years ago - 2 comments

#98 - Ignore bad value for state variable when handling a GENA event

Pull Request - State: closed - Opened by lolodomo over 6 years ago - 2 comments

#98 - Ignore bad value for state variable when handling a GENA event

Pull Request - State: closed - Opened by lolodomo over 6 years ago - 2 comments

#97 - GENA message fully ignored if there is a data type problem for one state variable

Issue - State: closed - Opened by lolodomo over 6 years ago - 3 comments

#97 - GENA message fully ignored if there is a data type problem for one state variable

Issue - State: closed - Opened by lolodomo over 6 years ago - 3 comments

#97 - GENA message fully ignored if there is a data type problem for one state variable

Issue - State: closed - Opened by lolodomo over 6 years ago - 3 comments

#97 - GENA message fully ignored if there is a data type problem for one state variable

Issue - State: closed - Opened by lolodomo over 6 years ago - 3 comments

#96 - Ported QueueingThreadPoolExecutor synchronization improvements from Eclipse Smarthome

Pull Request - State: closed - Opened by velichkos over 6 years ago - 3 comments

#96 - Ported QueueingThreadPoolExecutor synchronization improvements from Eclipse Smarthome

Pull Request - State: closed - Opened by velichkos over 6 years ago - 3 comments

#96 - Ported QueueingThreadPoolExecutor synchronization improvements from Eclipse Smarthome

Pull Request - State: closed - Opened by velichkos over 6 years ago - 3 comments

#96 - Ported QueueingThreadPoolExecutor synchronization improvements from Eclipse Smarthome

Pull Request - State: closed - Opened by velichkos over 6 years ago - 3 comments

#96 - Ported QueueingThreadPoolExecutor synchronization improvements from Eclipse Smarthome

Pull Request - State: closed - Opened by velichkos over 6 years ago - 3 comments

#96 - Ported QueueingThreadPoolExecutor synchronization improvements from Eclipse Smarthome

Pull Request - State: closed - Opened by velichkos over 6 years ago - 3 comments

#96 - Ported QueueingThreadPoolExecutor synchronization improvements from Eclipse Smarthome

Pull Request - State: closed - Opened by velichkos over 6 years ago - 3 comments

#95 - stop tampering with the preferIPv4Stack system property

Pull Request - State: closed - Opened by sjsf over 6 years ago - 2 comments

#95 - stop tampering with the preferIPv4Stack system property

Pull Request - State: closed - Opened by sjsf over 6 years ago - 2 comments

#95 - stop tampering with the preferIPv4Stack system property

Pull Request - State: closed - Opened by sjsf over 6 years ago - 2 comments

#95 - stop tampering with the preferIPv4Stack system property

Pull Request - State: closed - Opened by sjsf over 6 years ago - 2 comments

#95 - stop tampering with the preferIPv4Stack system property

Pull Request - State: closed - Opened by sjsf over 6 years ago - 2 comments