Attempt to make replaying work in the general situation

simplify a bit the code (vlorentz' suggestion)

rebase

rebase

also rename ProvenanceInterface.directory_xxx_flattenned as directory_xxx_flattened

rebase

apply vlorentz' comments

lgtm

rebase

lgtm

LGTM, thanks

Remove the fallback to 127.0.0.1:25 but log delivery failure instead

apply olasd's suggestions

FTR, using order by age():

FTR here a dot export of the directory profiling file:

rename http_server.py as http_rpc_server.py and use the same http_rpc_server config entry name (as suggested by vlorentz)

In D8448#219434, @vlorentz wrote:

what about http_rpc_server instead of rpc_server (in the config) and http_server (as module name), to remove any ambiguity?

rebase

lgtm but would it make sense to test cases with usage of this new option combined with other limiting params ({min,max}_depth and max_edges)?

IMHO we should get rid of the java app being started from python (but for testing purpose).

ok (but I have a couple of questions)

In D8362#217751, @vlorentz wrote:

Can you generate these files on the fly using a pytest fixture?

rebase and add forgoten generate_graph_dataset.py tool

add a forgoten dataset visit file

rebase