From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] seafile-cli broken
Date: Thu, 21 Jan 2021 18:26:42 +0100 [thread overview]
Message-ID: <20210121172642.B91TX8_ldXL4gZGHoNhzfVh0x7INplGynRuaMLhgwdo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28041@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]
Closed issue by WasabiPizza on void-packages repository
https://github.com/void-linux/void-packages/issues/28041
Description:
### System
* xuname:
Void 5.10.8_1 x86_64-musl GenuineIntel uptodate rrnFF
* package:
seafile-cli-7.0.10_1
Just running `seaf-cli` should produce the error.
I thought it was fixed running `pip install -U future` (thanks to who helped me on irc, can't remeber the name sorry) but now, when I try running `seaf-cli sync ...` I get:
```
Starting to download ...
Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/pysearpc/named_pipe.py", line 88, in _get_transport
transport = self._pool.get(False)
File "/usr/lib/python3.9/queue.py", line 168, in get
raise Empty
_queue.Empty
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/bin/seaf-cli", line 983, in <module>
main()
File "/bin/seaf-cli", line 979, in main
args.func(args)
File "/bin/seaf-cli", line 680, in seaf_sync
seafile_rpc.clone(repo,
File "/usr/lib/python3.9/site-packages/pysearpc/client.py", line 126, in newfunc
ret_str = self.call_remote_func_sync(fcall_str)
File "/usr/lib/python3.9/site-packages/pysearpc/named_pipe.py", line 100, in call_remote_func_sync
transport = self._get_transport()
File "/usr/lib/python3.9/site-packages/pysearpc/named_pipe.py", line 90, in _get_transport
transport = self._create_transport()
File "/usr/lib/python3.9/site-packages/pysearpc/named_pipe.py", line 83, in _create_transport
transport.connect()
File "/usr/lib/python3.9/site-packages/pysearpc/named_pipe.py", line 47, in connect
self.pipe.connect(self.socket_path)
ConnectionRefusedError: [Errno 111] Connection refused
```
Thanks!
next prev parent reply other threads:[~2021-01-21 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 21:52 [ISSUE] " WasabiPizza
2021-01-19 22:10 ` ericonr
2021-01-19 22:12 ` ericonr
2021-01-19 22:18 ` WasabiPizza
2021-01-19 22:23 ` ericonr
2021-01-19 22:31 ` WasabiPizza
2021-01-20 2:07 ` sgn
2021-01-20 21:19 ` yopito
2021-01-20 21:53 ` yopito
2021-01-21 17:26 ` ericonr [this message]
2021-01-21 22:35 ` WasabiPizza
2021-01-22 16:08 ` yopito
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210121172642.B91TX8_ldXL4gZGHoNhzfVh0x7INplGynRuaMLhgwdo@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).