Juan Quintela wrote:
> Tejus GK wrote:
>> On 04/10/23 1:53 pm, Juan Quintela wrote:
>>> Tejus GK wrote:
On 03/10/23 6:14 pm, Juan Quintela wrote:
> Ouch, that again.
>
> I think that I know how to fix that.
>
> Will take a look.
>
> Later, Juan.
I first only saw that you were missing migra
Tejus GK wrote:
> On 04/10/23 1:53 pm, Juan Quintela wrote:
>> Tejus GK wrote:
>>> On 03/10/23 6:14 pm, Juan Quintela wrote:
Tejus GK wrote:
> A few code paths exist in the source code,where a migration is
> marked as failed via MIGRATION_STATUS_FAILED, but the failure happens
>
On 04/10/23 1:53 pm, Juan Quintela wrote:
Tejus GK wrote:
On 03/10/23 6:14 pm, Juan Quintela wrote:
Tejus GK wrote:
A few code paths exist in the source code,where a migration is
marked as failed via MIGRATION_STATUS_FAILED, but the failure happens
outside of migration.c
In such cases, an e
Tejus GK wrote:
> On 03/10/23 6:14 pm, Juan Quintela wrote:
>> Tejus GK wrote:
>>> A few code paths exist in the source code,where a migration is
>>> marked as failed via MIGRATION_STATUS_FAILED, but the failure happens
>>> outside of migration.c
>>>
>>> In such cases, an error_report() c
On 03/10/23 6:14 pm, Juan Quintela wrote:
Tejus GK wrote:
A few code paths exist in the source code,where a migration is
marked as failed via MIGRATION_STATUS_FAILED, but the failure happens
outside of migration.c
In such cases, an error_report() call is made, however the current
MigrationStat
Tejus GK wrote:
> A few code paths exist in the source code,where a migration is
> marked as failed via MIGRATION_STATUS_FAILED, but the failure happens
> outside of migration.c
>
> In such cases, an error_report() call is made, however the current
> MigrationState is never updat
A few code paths exist in the source code,where a migration is
marked as failed via MIGRATION_STATUS_FAILED, but the failure happens
outside of migration.c
In such cases, an error_report() call is made, however the current
MigrationState is never updated with the error description, and hence
clien
