b13 / content-sync Goto Github PK

following scenario:

1. be_user updates password
2. sync starts to prod/dev instance
3. MFA und new password are working instantly on all other envs

I've set up an automatically created sync that runs at 2 AM and the scheduler shows that the job was created at the configured time.
15-07-22 02:02 (Cron)

But the info in the toolbar seems to miss the timezone and shows this date for that job

Finished at: 07/15/2022 12:13:09
Execution Time: 401 Seconds

This seems to miss the current timezone offset and also h instead of H for the hours feels a bit unusual.
The timezone is set to Europe/Berlin, so maybe something is a bit off here

The sync processes are created with the default timeout of 60s

$process = Process::fromShellCommandline($cmd);

This might not be enough for slow servers/connections or initial sync runs. Can the timeout be increased or made configurable from the ext config? My DB imports unfortunately take a bit longer then 60s

public static function fromShellCommandline(string $command, string $cwd = null, array $env = null, $input = null, ?float $timeout = 60)

Syncing Content from a v10 source to a v11 target, failing by the cache flush (groups/tags) command.

Maybe detecting the Version should be done directly on the remote or an Option to override the Version-Check in the Extension Configuration would be great to avoid this problem.