You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug, including details regarding any error messages, version, and platform.
version: pyarrow 13.0.0
error stack:
location: Location = Location.for_grpc_tcp(host="[::]", port=5005)
server = FlightServer(args.host, location,
tls_certificates=tls_certificates,
verify_client=args.verify_client)
super(FlightServer, self).__init__(
File "pyarrow/_flight.pyx", line 2765, in pyarrow._flight.FlightServerBase.__init__
File "pyarrow/_flight.pyx", line 2838, in pyarrow._flight.FlightServerBase.init
File "pyarrow/_flight.pyx", line 78, in pyarrow._flight.check_flight_status
File "pyarrow/error.pxi", line 100, in pyarrow.lib.check_status
pyarrow.lib.ArrowInvalid: Cannot parse URI: 'grpc+tcp://:::5005'
I see that it has been fixed in #8585, but it still seems to be unresolved in pyarrow, or is there a mistake in the way I use it?
The started service will listen to ipv6 and can support ipv6 client requests. But it cannot support listening to the specified ip
netstat -tlnp | grep 5005
tcp6 0 0 :::5005 :::* LISTEN 853314/python
client work with ipv6: [::1]:5005
Component(s)
Python
The text was updated successfully, but these errors were encountered:
### Rationale for this change
Binding to an IPv6 address got broken along the way
### What changes are included in this PR?
Fix the binding and see if we can enable IPv6 testing in CI
### Are these changes tested?
If CI permits
### Are there any user-facing changes?
No
* Closes: #37539
Authored-by: David Li <li.davidm96@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
…e#37552)
### Rationale for this change
Binding to an IPv6 address got broken along the way
### What changes are included in this PR?
Fix the binding and see if we can enable IPv6 testing in CI
### Are these changes tested?
If CI permits
### Are there any user-facing changes?
No
* Closes: apache#37539
Authored-by: David Li <li.davidm96@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
dgreiss
pushed a commit
to dgreiss/arrow
that referenced
this issue
Feb 19, 2024
…e#37552)
### Rationale for this change
Binding to an IPv6 address got broken along the way
### What changes are included in this PR?
Fix the binding and see if we can enable IPv6 testing in CI
### Are these changes tested?
If CI permits
### Are there any user-facing changes?
No
* Closes: apache#37539
Authored-by: David Li <li.davidm96@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Describe the bug, including details regarding any error messages, version, and platform.
version: pyarrow 13.0.0
error stack:
I see that it has been fixed in #8585, but it still seems to be unresolved in pyarrow, or is there a mistake in the way I use it?
The started service will listen to ipv6 and can support ipv6 client requests. But it cannot support listening to the specified ip
Component(s)
Python
The text was updated successfully, but these errors were encountered: