thx

Build is green

@anlambert Can you have a look too?

add typeann + rebase

Build is green

align docstring

Build is green

Fix tests (i forgot one adaptation in another test)

Build has FAILED

Improve implementations:

• add tests
• add types

Everything looks good with logstash 1:7.15.1
The monitoring of the logstash errors is still working as previously:

root@logstash0:/usr/lib/nagios/plugins/swh# ./check_logstash_errors.sh 
OK - No errors detected

after closing the current system index:

root@logstash0:/usr/lib/nagios/plugins/swh# ./check_logstash_errors.sh 
CRITICAL - Logstash has detected some errors in outputs errors=9 non_retryable_errors=13

To upgrade kibana, upgrading the version looks enough. The migration is automatically done and all the configured elements are still available:

root@esnode1:~# curl -s http://10.168.100.61:9200/_cat/indices\?v=true\&s=index | grep kibana
health status index                           uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   .kibana-event-log-7.15.1-000001 24Wb0rfUQuqab3Iody3Hrg   1   1          1            0     12.1kb            6kb  <-------- new index
green  open   .kibana-event-log-7.8.0-000001  6IjHICQVS2uX8qBekJLWsw   1   1          2            0     21.4kb         10.7kb
green  open   .kibana_2                       Oh9O6uB1R0-oNPbnhTM8kw   1   1       1928            3      1.5mb        788.4kb
green  open   .kibana_7.15.1_001              5fyk6NMUSE-3P6uhx-HSeg   1   1       1110           35      5.3mb          2.6mb  <-------- new index (automatically migrated from kibana_2)
green  open   .kibana_task_manager_1          vINZFVqCSJiDHHFMdYGwTA   1   1          5            0       32kb           16kb
green  open   .kibana_task_manager_7.15.1_001 pYeR_zFdTZO_jqxYS1DB9g   1   1         16          369      527kb        277.5kb  <-------- new index

root@esnode1:~# curl -s http://10.168.100.61:9200/_cat/aliases\?v=true\&s=index | grep kibana
alias                       index                           filter routing.index routing.search is_write_index
.kibana-event-log-7.15.1    .kibana-event-log-7.15.1-000001 -      -             -              true
.kibana-event-log-7.8.0     .kibana-event-log-7.8.0-000001  -      -             -              true
.kibana                     .kibana_7.15.1_001              -      -             -              -
.kibana_7.15.1              .kibana_7.15.1_001              -      -             -              -
.kibana_task_manager        .kibana_task_manager_7.15.1_001 -      -             -              -
.kibana_task_manager_7.15.1 .kibana_task_manager_7.15.1_001 -      -             -              -

Build is green

Could you document the expected shard layout in RestructuredText format? This code is setting the (current version of the) layout "forever", so we should make sure to properly document it.

Diffs landed, packaged and deployed.
Closing.

Is the request for regular pulling?

In T1538#73659, @moranegg wrote:

Is the request for regular pulling?
If yes, it should be added for visibility on the home page of the archive.
If no, it should be clear this is a one shot thing.

@posenato Hello, i was gonna check this morning and ping you to let you know.

Yannick hasn't answered yet. Will try again on the 15th.

I'm not sure where we are at on this evolution.
Maybe we can discuss this next week.

This is an example of a use-case in Open Science:
An institution has a forge and wishes to add the forge as a whole to SWH.

• https://gricad-gitlab.univ-grenoble-alpes.fr/explore
• https://gitlab.inria.fr/explore

It has just finished saving the repository.
It worked perfectly.
Thank you a lot for your support.

All fixes have currently landed, got packaged in v0.7.3.
I've deployed it and triggered a run [1] for the origin (ongoing).

Build is green

• tests: Actually check the last visit is indeed a full visit

Build is green

Fix test no longer happy after the rebase introducing the post_load implementation

The migration of ES can be performed with:

1. elasticsearch migration

There is one change in behavior: svn_special_path_non_link_data is reset at the same time as eol_style for a file. I assume it was an oversight not to do it before this diff

Can you please add types to the constructor parameter you updated?

Build has FAILED

Rebase on latest master

Remains 1 origin still ongoing... almost there...

Build is green

delete states recursively again

In order to validate the kibana upgrade, the kibana configuration can be copied locally with these commands:

Build is green

rebase

Build is green

nevermind, I had an uncommitted change somewhere

rebase

Some generic comments on the C side:

Build is green

fix docstring rst syntax

Build has FAILED

Build is green

Build is green

apply vlorentz' comments

rebase

Use a hardwritten list of accepted objects

The preparation of the migration through the vagrant environment is in progress.

Thanks for the info.
For the record, the entry point of the upgrade process: https://www.elastic.co/guide/en/elastic-stack/current/upgrading-elastic-stack.html

Build is green

Rebase

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