Build is green

I'm getting this when running the test on my machine, any idea why?

Build has FAILED

fix bad copy-paste in test example

lgtm

Any idea why this happens?

I'd make the debug message into an info one but that's fine as it is.

Here is an overview of the fields (+ internal version name + branch name) used by each package loader, after D6616:

The basic auth is working with the default remote implementation if the credentials are specified in the url like https://user:password@objstorage_url

not on the cassandra side

Closing to avoid diff clutter.

good idea.

@vsellier Did you have swh-graph enabled in the vault configuration for these benchmarks?

In D6395#171365, @borisbaldassari wrote:

I will let you know when the full chain is executed.

On the three hypervisors currently running workers (hypervisor3, branly, pompidou), I've created a thin LVM pool for scratch data, using the following commands:

I've kicked a SSD out of branly and hypervisor3's ceph allocation; ceph is currently rebalancing.

Status update:

FWIW the main blocker for upgrading journalbeat is a change in the target mapping, which will need some adaptations in our log routing (between systemlogs and swh_workers), as well as, well, an updated mapping on the target indexes!

Build is green

Build is green

Build is green

• apply style change in fetch_rlog() suggested by vlorentz

Update license header

Build is green

Update: Ensure to pass a valid url to URL constructor and encode path query parameter value

fix mypy errors with much help from vlorentz

Build is green

add docstring to cvsclient's checkout() function

In D6614#171828, @vlorentz wrote:

Then when doing this:

directoryUrl += `?path=${path}`;

directoryUrl will end with ?path=/path&/foo and that's not good

Build is green

Then when doing this:

removed cvsclient.py test code

In D6614#171796, @vlorentz wrote:

What if there is a & character in the path?

Not an issue, URL object will correctly parse it as part of the path.

>>> s = "http://example.org/path&/foo?service=swh&query=bar"
"http://example.org/path&/foo?service=swh&query=bar"
>>> new URL(s)
URL { href: "http://example.org/path&/foo?service=swh&query=bar", origin: "http://example.org", protocol: "http:", username: "", password: "", host: "example.org", hostname: "example.org", port: "", pathname: "/path&/foo", search: "?service=swh&query=bar" }
​

What if there is a & character in the path?