Attributes migration error from cloud to self-hosted

[celest hare]

Hi, I was migrating the data from cloud to a self-hosted instance. Almost all the data does migrate successfully except for a few attributes. Those two attributes are of type double (if that helps).

[celest hare]

The same issue occurs when migrating from one self-hosted instance to other. But this time only one attribute error and that to it is of type double (float).

[sacred sinew]

interesting...any other logs?

maybe in the appwrite-worker-migrations container?

[celest hare]

This is the error I get in the migration details popup:
"Failed to transfer resource ':attribute' with message 'Attribute creation timeout'"

[celest hare]

How can I get their logs? Not much familiar with Docker

[sacred sinew]

What exactly is the attribute? The databases worker might also have some helpful logs too

[sacred sinew]

https://appwrite.io/docs/advanced/self-hosting/debug#logs

[celest hare]

The attribute is a float with default value 0 and no min and max values defined (since they aren't mandatory while creating the attribute)

[sacred sinew]

what's the key?

[celest hare]

The key is "rating"

[sacred sinew]

ya that seems normal..

[sacred sinew]

there should be some logs about why the attribute failed to create. another thing you check is the JSON response from the list collections API. there should be a log attribute on the attribute object

[celest hare]

   {
               "databaseInternalId":"1",
               "databaseId":"65265b9d65617f5e0e9c",
               "collectionInternalId":"5",
               "collectionId":"ServiceProviders",
               "key":"rating",
               "type":"double",
               "status":"failed",
               "error":"Default value 0 does not match given type double",
               "size":0,
               "required":false,
               "default":0,
               "signed":true,
               "array":false,
               "format":"floatRange",
               "formatOptions":{
                  "min":-1.7976931348623157e+308,
                  "max":1.7976931348623157e+308
               },

I went through the database container logs and this is what I found

I think it was expecting "0.0" as the value but instead it got "0". Hence it failed

[sacred sinew]

interesting...

i thought it was going to fail on max/min 😆

[celest hare]

Initially I too thought the same because when I tried editing the failed attribute from the console, it was saying that the min and max value is invalid

Another thing to note is that it fails only when the value is 0 or single digit and not some other double