That's been done for years now.

There is no longer any debian branches on the swh-graph repository, so this must have been done already.

 swh  tony  yavin4  ~  work  …  swh  swh-environment  swh-graph   master  1⚑  ERROR  %  git pull
Already up to date.
 swh  tony  yavin4  ~  work  …  swh  swh-environment  swh-graph   master  1⚑  %  git branch --remote | grep -i debian
 swh  tony  yavin4  ~  work  …  swh  swh-environment  swh-graph   master  1⚑  ERROR  %  git branch --remote | grep -i upstream
 swh  tony  yavin4  ~  work  …  swh  swh-environment  swh-graph   master  1⚑  ERROR  %  git branch --remote | grep -i pristine-tar

We should also build the whole documentation when submitting a diff to swh-docs, some sphinx errors not related to packages documentation could be caught this way (see https://jenkins.softwareheritage.org/job/DDOC/job/dev/5700/artifact/swh-docs/docs/errors.log)

Solution 3 has been implemented through new tox environments in each swh package.

So either the vault is fine and the test needs to be improved.
Or the vault builds the tarball without taking into account the symlink case.

@rendong951 Sorry, but we can't reproduce the issue on our end.

I also try command fllowing your reply，the results are the same.

It's not a DNS issue. The error is Could not resolve hostname https:. It shouldn't try to resolve https:, it's a scheme, not a domain name.

Thank you very much for your reply.
I followed your command.[1]

Please wrap your stacktrace, excerpt of code, etc... with triple backquote before and after.
So this becomes more readable.
Thanks in advance.

Thank you very much for your reply.
And I follow your guidance，now，all the services are started，but when I save code in my Software Heritage platform, the status always failed, I checked log :
swh-loader_1 | [2020-12-18 02:49:13,495: ERROR/ForkPoolWorker-1] Loading failure, updating to partial status
swh-loader_1 | Traceback (most recent call last):
swh-loader_1 | File "/srv/softwareheritage/venv/lib/python3.7/site-packages/dulwich/client.py", line 912, in fetch_pack
swh-loader_1 | refs, server_capabilities = read_pkt_refs(proto)
swh-loader_1 | File "/srv/softwareheritage/venv/lib/python3.7/site-packages/dulwich/client.py", line 215, in read_pkt_refs
swh-loader_1 | for pkt in proto.read_pkt_seq():
swh-loader_1 | File "/srv/softwareheritage/venv/lib/python3.7/site-packages/dulwich/protocol.py", line 277, in read_pkt_seq
swh-loader_1 | pkt = self.read_pkt_line()
swh-loader_1 | File "/srv/softwareheritage/venv/lib/python3.7/site-packages/dulwich/protocol.py", line 223, in read_pkt_line
swh-loader_1 | raise HangupException()
swh-loader_1 | dulwich.errors.HangupException: The remote server unexpectedly closed the connection.
swh-loader_1 |
swh-loader_1 | During handling of the above exception, another exception occurred:
swh-loader_1 |
swh-loader_1 | Traceback (most recent call last):
swh-loader_1 | File "/srv/softwareheritage/venv/lib/python3.7/site-packages/swh/loader/core/loader.py", line 318, in load
swh-loader_1 | more_data_to_fetch = self.fetch_data()
swh-loader_1 | File "/srv/softwareheritage/venv/lib/python3.7/site-packages/swh/loader/git/loader.py", line 239, in fetch_data
swh-loader_1 | self.origin.url, self.base_snapshot, do_progress
swh-loader_1 | File "/srv/softwareheritage/venv/lib/python3.7/site-packages/swh/loader/git/loader.py", line 174, in fetch_pack_from_origin
swh-loader_1 | progress=do_activity,
swh-loader_1 | File "/srv/softwareheritage/venv/lib/python3.7/site-packages/dulwich/client.py", line 914, in fetch_pack
swh-loader_1 | raise _remote_error_from_stderr(stderr)
swh-loader_1 | dulwich.errors.HangupException: ssh: Could not resolve hostname https: Temporary failure in name resolution

Thanks for opening this issue.

All repositories have been successfully processed, closing this.

awesome, thanks.

Ok so I applied the above process locally and no bad surprises when running all test suites. I will push the changes to remote then and close that task once it is done.

Ok so the plan to integrate isort in all repos will be the following:

1. Integrate the following diff (manually) in all repos using the change-all-repos script from @vlorentz but do not push to remote yet

diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index 5ab0e08..df70797 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -26,6 +26,11 @@ repos:
     language: system
     types: [python]

You might need to skip .py files in tests/*/data (eg. swh-web iirc)

(I was initially surprised by the mixing together of "import" lines with "from ... import" ones, but upon reflection it makes a lot of sense, because one might have to switch between the two forms, and it's silly to have to move the line back and forth between import blocks when that happens.)

You might need to skip .py files in tests/*/data (eg. swh-web iirc)

+1 to the idea (and to the specific config as I have already bikeshed it)

Let's consider this done for now. Still not "great" loading time, but much better than before.