Publishing fails with code 400 /api/version

[emilianya]

I am using electron-forge to publish to ERS, my builds worked fine for 30 or so updates, and then started failing on all but 1 platform.
Linux builds work fine since they finish first, but mac and windows builds fail with this error.

After a bit of testing i found that the response is as follows:

{
    "code": "E_UNIQUE",
    "message": "Would violate uniqueness constraint-- a record already exists with conflicting value(s).",
    "modelIdentity": "version",
    "attrNames": [
        "id"
    ]
}

The only successful api responses i have gotten have the id in the format of 0.1.0_null, even though the api request specifies something else after the _

[greenbeam-ita]

I got the same

[emilianya]

my solution was to completely wipe the database, then it started functioning again.

that is obviously not a good solution

[emilianya]

Alrighty i hit version 0.1.34 and it exploded again
19|ers | verbo: Sending 400 ("Bad Request") response:
19|ers | AdapterError: Would violate uniqueness constraint-- a record already exists with conflicting value(s).

well about a month ago but i got lazy and annoyed so I just ignored the issue

[payneWeave]

We believe there is some kind of default limit on the number of versions that get returned on the /api/version endpoint. For us we found it to be roughly 30. The endpoint also isn't sorted so it isn't deterministic as to when you will experience the issue.

I believe the fix is to either keep your list of versions smaller than 30, or add a sort function to the default sails response for /api/version sorting on updatedAt should do the trick.

[payneWeave]

Related issue in electron-forge: electron/forge#3430
Related PR to fix the issue in electron-forge: electron/forge#3431
Related issue in sails.js: balderdashy/sails#6542