[SOLVED] Bug Report: Cannot deploy collections in appwrite.json with Int Attributes

[drowsy fjord]

Hi. I'm creating a collection via appwrite cli from appwrite.json but it's returning "✗ Error Invalid min param: Value must be a valid integer" and "✗ Error Invalid max param: Value must be a valid integer" for min/max fields that have been set to
{
"key": "createdAt",
"type": "integer",
"status": "available",
"required": true,
"array": false,
"min": -9223372036854776000,
"max": 9223372036854776000,
"default": null
}
It's from this repo https://github.com/Meldiron/almost-cookie-store and article https://dev.to/appwrite/start-selling-online-using-appwrite-and-stripe-3l04 but the instructions and repo are deprecated, but I'm trying to get it to work as a demo to test out stripe integration, as there don't seem to be any others available.

Ok, this seems to be the same error as https://github.com/appwrite/appwrite/issues/2894 which was reported Mar 4, 2022 and still seems unfixed.
Is there a solution?

I've added a comment to the github bug report as well.

[native marsh]

Should the values not be -9223372036854775808 and 9223372036854775808? As that is the max integer value?

[rotund parcel]

The bug you’ve linked was about the min/max parameters being generated incorrectly, not about these incorrect values failing deployment (which is intended behaviour). As @native marsh said, replace the min and max parameters with the numbers he gave.

[drowsy fjord]

I'll try that, thanks.

@rotund parcel Don't shoot the messenger. The bug I linked literally says "Cannot deploy collections in appwrite.json with Int Attributes" and is related to the issue, as multiple others in the bug report have the same problem.
I'm just trying to get clarity on what the issue is, as Kenny clarified.

[rotund parcel]

That is correct - the user who opened the Issue did indeed think that the bug was in the import process. However, as I explained above, the bug was actually in the export process - so though the bug has been fixed, it didn't help you because the export was before that.

[drowsy fjord]

The problem was resolved from my POV, so works for me. It was the closest I could find to the issue, and was pretty much the issue as I experienced it.
In any event, deployment seems unreliable anyway. Tried multiple times now and it just comes back ✗ Error Attribute deletion did not finish for too long. (so deleted collection manually to retry as a test) or hangs on a 500 error. I guess it's early days for the cloud so will take some time to settle down.

Systems says all ok https://status.appwrite.online/ but get ✗ Error Server Error now.

Whatever I guess, it's a different issues, so please close this or delete it. Thanks.

[mint parcel]

Could you please create a new post here for that?

[SOLVED] Bug Report: Cannot deploy collections in appwrite.json with Int Attributes

[crisp smelt]

Is someone working on the other manifestations of this issue?

For me, it's happening in the console when creating/editing database attributes.

If I create an Integer attribute (in the 1.5.4 console) and leave min/max blank, it saves successfully. But when I come back later to edit the attribute, the min/max values are populated with min: -9223372036854776000 and max: 9223372036854776000 and when I attempt to save my edit, an error message pops up saying "Invalid min param: Value must be a valid integer" and I can't save until I leave the page and go look up what the minimum value for an integer is, then come back and change it.

Even once the bug that creates the incorrect value is fixed, it would be nice if the screen advised the user what the actual minimum and maximum values are (if not all the time, then at least in the error message).

[marsh python]

Reopened and transferred to CLI repo: https://github.com/appwrite/sdk-for-cli/issues/124