Ecosyste.ms: Issues

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

GitHub / kohlschutter/junixsocket issues and pull requests

#69 - java: symbol lookup error: /tmp/libtmp8709324396123266813libjunixsocket-native-2.2.0.so: undefined symbol: stat

Issue - State: closed - Opened by 137268431 over 5 years ago - 6 comments
Labels: bug, information needed

#68 - Add support for Linux on PowerPC 64-bit LE (ppc64le)

Pull Request - State: closed - Opened by sriemer over 5 years ago - 4 comments
Labels: verify

#68 - Add support for Linux on PowerPC 64-bit LE (ppc64le)

Pull Request - State: closed - Opened by sriemer over 5 years ago - 4 comments
Labels: verify

#68 - Add support for Linux on PowerPC 64-bit LE (ppc64le)

Pull Request - State: closed - Opened by sriemer over 5 years ago - 4 comments
Labels: verify

#68 - Add support for Linux on PowerPC 64-bit LE (ppc64le)

Pull Request - State: closed - Opened by sriemer over 5 years ago - 4 comments
Labels: verify

#68 - Add support for Linux on PowerPC 64-bit LE (ppc64le)

Pull Request - State: closed - Opened by sriemer over 5 years ago - 4 comments
Labels: verify

#68 - Add support for Linux on PowerPC 64-bit LE (ppc64le)

Pull Request - State: closed - Opened by sriemer over 5 years ago - 4 comments
Labels: verify

#68 - Add support for Linux on PowerPC 64-bit LE (ppc64le)

Pull Request - State: closed - Opened by sriemer over 5 years ago - 4 comments
Labels: verify

#68 - Add support for Linux on PowerPC 64-bit LE (ppc64le)

Pull Request - State: closed - Opened by sriemer over 5 years ago - 4 comments
Labels: verify

#68 - Add support for Linux on PowerPC 64-bit LE (ppc64le)

Pull Request - State: closed - Opened by sriemer over 5 years ago - 4 comments
Labels: verify

#67 - Is junixsocket supported on ppc64le

Issue - State: closed - Opened by rashmi-sakhalkar over 5 years ago - 22 comments
Labels: verify

#67 - Is junixsocket supported on ppc64le

Issue - State: closed - Opened by rashmi-sakhalkar over 5 years ago - 22 comments
Labels: verify

#67 - Is junixsocket supported on ppc64le

Issue - State: closed - Opened by rashmi-sakhalkar over 5 years ago - 22 comments
Labels: verify

#67 - Is junixsocket supported on ppc64le

Issue - State: closed - Opened by rashmi-sakhalkar over 5 years ago - 22 comments
Labels: verify

#67 - Is junixsocket supported on ppc64le

Issue - State: closed - Opened by rashmi-sakhalkar over 5 years ago - 22 comments
Labels: verify

#67 - Is junixsocket supported on ppc64le

Issue - State: closed - Opened by rashmi-sakhalkar over 5 years ago - 22 comments
Labels: verify

#67 - Is junixsocket supported on ppc64le

Issue - State: closed - Opened by rashmi-sakhalkar over 5 years ago - 22 comments
Labels: verify

#67 - Is junixsocket supported on ppc64le

Issue - State: closed - Opened by rashmi-sakhalkar over 5 years ago - 22 comments
Labels: verify

#67 - Is junixsocket supported on ppc64le

Issue - State: closed - Opened by rashmi-sakhalkar over 5 years ago - 22 comments
Labels: verify

#66 - java.net.SocketException: Protocol wrong type for socket

Issue - State: closed - Opened by adamtg over 5 years ago - 2 comments

#66 - java.net.SocketException: Protocol wrong type for socket

Issue - State: closed - Opened by adamtg over 5 years ago - 2 comments

#66 - java.net.SocketException: Protocol wrong type for socket

Issue - State: closed - Opened by adamtg over 5 years ago - 2 comments

#66 - java.net.SocketException: Protocol wrong type for socket

Issue - State: closed - Opened by adamtg over 5 years ago - 2 comments

#66 - java.net.SocketException: Protocol wrong type for socket

Issue - State: closed - Opened by adamtg over 5 years ago - 2 comments

#66 - java.net.SocketException: Protocol wrong type for socket

Issue - State: closed - Opened by adamtg over 5 years ago - 2 comments

#66 - java.net.SocketException: Protocol wrong type for socket

Issue - State: closed - Opened by adamtg over 5 years ago - 2 comments

#66 - java.net.SocketException: Protocol wrong type for socket

Issue - State: closed - Opened by adamtg over 5 years ago - 2 comments

#66 - java.net.SocketException: Protocol wrong type for socket

Issue - State: closed - Opened by adamtg over 5 years ago - 2 comments

#66 - java.net.SocketException: Protocol wrong type for socket

Issue - State: closed - Opened by adamtg over 5 years ago - 2 comments

#66 - java.net.SocketException: Protocol wrong type for socket

Issue - State: closed - Opened by adamtg over 5 years ago - 2 comments

#65 - java8 target

Issue - State: closed - Opened by KostyaSha almost 6 years ago - 4 comments

#65 - java8 target

Issue - State: closed - Opened by KostyaSha almost 6 years ago - 4 comments

#64 - RFC: Compilation fixes for openSUSE

Pull Request - State: closed - Opened by sriemer almost 6 years ago - 1 comment

#64 - RFC: Compilation fixes for openSUSE

Pull Request - State: closed - Opened by sriemer almost 6 years ago - 1 comment

#64 - RFC: Compilation fixes for openSUSE

Pull Request - State: closed - Opened by sriemer almost 6 years ago - 1 comment

#63 - Bug: AcceptTimeoutTest fails with Oracle JDK11 on openSUSE Leap 15.1

Issue - State: closed - Opened by sriemer almost 6 years ago - 4 comments
Labels: bug, verify

#63 - Bug: AcceptTimeoutTest fails with Oracle JDK11 on openSUSE Leap 15.1

Issue - State: closed - Opened by sriemer almost 6 years ago - 4 comments
Labels: bug, verify

#63 - Bug: AcceptTimeoutTest fails with Oracle JDK11 on openSUSE Leap 15.1

Issue - State: closed - Opened by sriemer almost 6 years ago - 4 comments
Labels: bug, verify

#63 - Bug: AcceptTimeoutTest fails with Oracle JDK11 on openSUSE Leap 15.1

Issue - State: closed - Opened by sriemer almost 6 years ago - 4 comments
Labels: bug, verify

#63 - Bug: AcceptTimeoutTest fails with Oracle JDK11 on openSUSE Leap 15.1

Issue - State: closed - Opened by sriemer almost 6 years ago - 4 comments
Labels: bug, verify

#63 - Bug: AcceptTimeoutTest fails with Oracle JDK11 on openSUSE Leap 15.1

Issue - State: closed - Opened by sriemer almost 6 years ago - 4 comments
Labels: bug, verify

#63 - Bug: AcceptTimeoutTest fails with Oracle JDK11 on openSUSE Leap 15.1

Issue - State: closed - Opened by sriemer almost 6 years ago - 4 comments
Labels: bug, verify

#63 - Bug: AcceptTimeoutTest fails with Oracle JDK11 on openSUSE Leap 15.1

Issue - State: closed - Opened by sriemer almost 6 years ago - 4 comments
Labels: bug, verify

#62 - libjunixsocket-native-{version}.so not generated on s390x.

Issue - State: closed - Opened by imdurgadas almost 6 years ago - 12 comments
Labels: enhancement, verify

#62 - libjunixsocket-native-{version}.so not generated on s390x.

Issue - State: closed - Opened by imdurgadas almost 6 years ago - 12 comments
Labels: enhancement, verify

#62 - libjunixsocket-native-{version}.so not generated on s390x.

Issue - State: closed - Opened by imdurgadas almost 6 years ago - 12 comments
Labels: enhancement, verify

#62 - libjunixsocket-native-{version}.so not generated on s390x.

Issue - State: closed - Opened by imdurgadas almost 6 years ago - 12 comments
Labels: enhancement, verify

#62 - libjunixsocket-native-{version}.so not generated on s390x.

Issue - State: closed - Opened by imdurgadas almost 6 years ago - 12 comments
Labels: enhancement, verify

#62 - libjunixsocket-native-{version}.so not generated on s390x.

Issue - State: closed - Opened by imdurgadas almost 6 years ago - 12 comments
Labels: enhancement, verify

#62 - libjunixsocket-native-{version}.so not generated on s390x.

Issue - State: closed - Opened by imdurgadas almost 6 years ago - 12 comments
Labels: enhancement, verify

#62 - libjunixsocket-native-{version}.so not generated on s390x.

Issue - State: closed - Opened by imdurgadas almost 6 years ago - 12 comments
Labels: enhancement, verify

#62 - libjunixsocket-native-{version}.so not generated on s390x.

Issue - State: closed - Opened by imdurgadas almost 6 years ago - 12 comments
Labels: enhancement, verify

#61 - keep the Maven module name in sync with the artifactId

Pull Request - State: closed - Opened by gesellix about 6 years ago - 1 comment

#61 - keep the Maven module name in sync with the artifactId

Pull Request - State: closed - Opened by gesellix about 6 years ago - 1 comment

#61 - keep the Maven module name in sync with the artifactId

Pull Request - State: closed - Opened by gesellix about 6 years ago - 1 comment

#61 - keep the Maven module name in sync with the artifactId

Pull Request - State: closed - Opened by gesellix about 6 years ago - 1 comment

#61 - keep the Maven module name in sync with the artifactId

Pull Request - State: closed - Opened by gesellix about 6 years ago - 1 comment

#61 - keep the Maven module name in sync with the artifactId

Pull Request - State: closed - Opened by gesellix about 6 years ago - 1 comment

#61 - keep the Maven module name in sync with the artifactId

Pull Request - State: closed - Opened by gesellix about 6 years ago - 1 comment

#61 - keep the Maven module name in sync with the artifactId

Pull Request - State: closed - Opened by gesellix about 6 years ago - 1 comment

#61 - keep the Maven module name in sync with the artifactId

Pull Request - State: closed - Opened by gesellix about 6 years ago - 1 comment

#60 - Question: what changed from 2.1.2 to 2.2.0?

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: question

#60 - Question: what changed from 2.1.2 to 2.2.0?

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: question

#60 - Question: what changed from 2.1.2 to 2.2.0?

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: question

#60 - Question: what changed from 2.1.2 to 2.2.0?

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: question

#60 - Question: what changed from 2.1.2 to 2.2.0?

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: question

#60 - Question: what changed from 2.1.2 to 2.2.0?

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: question

#60 - Question: what changed from 2.1.2 to 2.2.0?

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: question

#59 - x86_64-MacOSX-gpp not in junixsocket-native-common-2.1.2

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: verify

#59 - x86_64-MacOSX-gpp not in junixsocket-native-common-2.1.2

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: verify

#59 - x86_64-MacOSX-gpp not in junixsocket-native-common-2.1.2

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: verify

#59 - x86_64-MacOSX-gpp not in junixsocket-native-common-2.1.2

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: verify

#59 - x86_64-MacOSX-gpp not in junixsocket-native-common-2.1.2

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: verify

#59 - x86_64-MacOSX-gpp not in junixsocket-native-common-2.1.2

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: verify

#59 - x86_64-MacOSX-gpp not in junixsocket-native-common-2.1.2

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: verify

#59 - x86_64-MacOSX-gpp not in junixsocket-native-common-2.1.2

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: verify

#59 - x86_64-MacOSX-gpp not in junixsocket-native-common-2.1.2

Issue - State: closed - Opened by gesellix about 6 years ago - 2 comments
Labels: verify

#58 - Random Segmentation Faults in 2.0.4

Issue - State: closed - Opened by CodingFabian about 6 years ago - 2 comments
Labels: verify

#58 - Random Segmentation Faults in 2.0.4

Issue - State: closed - Opened by CodingFabian about 6 years ago - 2 comments
Labels: verify

#58 - Random Segmentation Faults in 2.0.4

Issue - State: closed - Opened by CodingFabian about 6 years ago - 2 comments
Labels: verify

#58 - Random Segmentation Faults in 2.0.4

Issue - State: closed - Opened by CodingFabian about 6 years ago - 2 comments
Labels: verify

#58 - Random Segmentation Faults in 2.0.4

Issue - State: closed - Opened by CodingFabian about 6 years ago - 2 comments
Labels: verify

#58 - Random Segmentation Faults in 2.0.4

Issue - State: closed - Opened by CodingFabian about 6 years ago - 2 comments
Labels: verify

#58 - Random Segmentation Faults in 2.0.4

Issue - State: closed - Opened by CodingFabian about 6 years ago - 2 comments
Labels: verify

#58 - Random Segmentation Faults in 2.0.4

Issue - State: closed - Opened by CodingFabian about 6 years ago - 2 comments
Labels: verify

#57 - Update/Fix Dependency Documentation Page (2.1.2)

Issue - State: closed - Opened by mina-asham about 6 years ago - 5 comments
Labels: bug, verify

#57 - Update/Fix Dependency Documentation Page (2.1.2)

Issue - State: closed - Opened by mina-asham about 6 years ago - 5 comments
Labels: bug, verify

#57 - Update/Fix Dependency Documentation Page (2.1.2)

Issue - State: closed - Opened by mina-asham about 6 years ago - 5 comments
Labels: bug, verify

#57 - Update/Fix Dependency Documentation Page (2.1.2)

Issue - State: closed - Opened by mina-asham about 6 years ago - 5 comments
Labels: bug, verify

#57 - Update/Fix Dependency Documentation Page (2.1.2)

Issue - State: closed - Opened by mina-asham about 6 years ago - 5 comments
Labels: bug, verify

#57 - Update/Fix Dependency Documentation Page (2.1.2)

Issue - State: closed - Opened by mina-asham about 6 years ago - 5 comments
Labels: bug, verify

#57 - Update/Fix Dependency Documentation Page (2.1.2)

Issue - State: closed - Opened by mina-asham about 6 years ago - 5 comments
Labels: bug, verify

#57 - Update/Fix Dependency Documentation Page (2.1.2)

Issue - State: closed - Opened by mina-asham about 6 years ago - 5 comments
Labels: bug, verify

#56 - WIP: attempt to test additional closed socket conditions discussed in

Pull Request - State: closed - Opened by dbyron0 about 6 years ago - 2 comments

#56 - WIP: attempt to test additional closed socket conditions discussed in

Pull Request - State: closed - Opened by dbyron0 about 6 years ago - 2 comments

#56 - WIP: attempt to test additional closed socket conditions discussed in

Pull Request - State: closed - Opened by dbyron0 about 6 years ago - 2 comments

#56 - WIP: attempt to test additional closed socket conditions discussed in

Pull Request - State: closed - Opened by dbyron0 about 6 years ago - 2 comments

#56 - WIP: attempt to test additional closed socket conditions discussed in

Pull Request - State: closed - Opened by dbyron0 about 6 years ago - 2 comments

#56 - WIP: attempt to test additional closed socket conditions discussed in

Pull Request - State: closed - Opened by dbyron0 about 6 years ago - 2 comments

#56 - WIP: attempt to test additional closed socket conditions discussed in

Pull Request - State: closed - Opened by dbyron0 about 6 years ago - 2 comments