Sails: Can't find log file like '.tmp/automigration.user.4844.log' after auto-migration failed

[LiuWei-Luke]

---

Sails version: 1.0.2
Node version: 8.11.1
NPM version: 5.6.0
DB adapter name: mongo
Operating system: MAC OS high sierra 10.13.3

Hi,

When I upgrade my project from sails 0.12 -> 1.0.2, forget change config migrate from
'alter' to 'safe'.

So it start migrate when I lift, and then error came out like:

When attempting to perform the alter auto-migration strategy on model document, Sails encountered incompatible data. Some existing document record(s) couldn't be adjusted automatically to match your model definition. Usually, this is a result of recent edits to your model files; or (less often) due to incomplete inserts or modifications made directly to the database by hand.

Details:

Failed to reinsert migrated data. Could not use one of the provided new records: Could not use specified `associatedPage`.  Expecting an id representing the associated record, or `null` to indicate there will be no associated record.  But the specified value is not a valid `associatedPage`.  Cannot use empty string ('') as a primary key value.

Some development data was recovered (see .tmp/automigration.document.4844.log). Any existing document records were deleted, but your data from OTHER models (including any relationships tracked in foreign keys and join tables) might still be intact. If you care about recovering any of that data, be sure to back it up now before you continue.

then my date was wiped, so I want try find the log file '.tmp/automigration.document.4844.log' to find data back, but can't find it in any where.

Is there any way I can find it?

[sailsbot]

Hi @LiuWei-Luke! It looks like you missed a step or two when you created your issue. Please edit your comment (use the pencil icon at the top-right corner of the comment box) and fix the following:

• Provide your DB adapter version
• Verify "I am experiencing a concrete technical issue (aka a bug) with Sails (ideas and feature proposals should follow the guide for proposing features and enhancements (http://bit.ly/sails-feature-guide), which involves making a pull request). If you're not 100% certain whether it's a bug or not, that's okay--you may continue. The worst that can happen is that the issue will be closed and we'll point you in the right direction."
• Verify "I am not asking a question about how to use Sails or about whether or not Sails has a certain feature (please refer to the documentation(http://sailsjs.com), or post on http://stackoverflow.com, our Google Group (http://bit.ly/sails-google-group) or our live chat (https://gitter.im/balderdashy/sails)."
• Verify "I have already searched for related issues, and found none open (if you found a related _closed_ issue, please link to it in your post)."
• Verify "My issue title is concise, on-topic and polite ("jst.js being removed from layout.ejs on lift" is good; "templates dont work" or "why is sails dumb" are not so good)."
• Verify "I have tried all the following (if relevant) and my issue remains:"
• Verify "I can provide steps to reproduce this issue that others can follow."

As soon as those items are rectified, post a new comment (e.g. “Ok, fixed!”) below and we'll take a look. Thanks!

*If you feel this message is in error, or you want to debate the merits of my existence (sniffle), please contact [email protected]

[johnabrams7]

Hi @LiuWei-Luke - I see you were running this project on a mac, did you have TimeMachine backup running before the upgrade? You may be able to recover any lost data with that or similar backup services, otherwise the data may be potentially changed/lost. Also check out the official Sails 1.x Upgrading doc for best practice if you haven't already, this covers important precautions and steps to take for upgrading. Hope this helps!

[johnabrams7]

@LiuWei-Luke - Hey, I just reproduced this issue on my side as well and indeed the automigration log file in is not generated in the .tmp folder from this scenario. This does appear to be a bug at the moment.

[mikermcneil]

Help welcome on this one- I remember vaguely seeing this before, and I think maybe it has to do with a regression due to something we did for fixing paths on windows

[lowe0292]

Hey just stopping by to say this bug is pretty brutal.

If you’re not going to fix this, you should at least update the console output to remove the message about the automigration file being written with the dumped data. It’s a really bad developer experience to go look for that file and find out it’s not there.

[rachaelshaw]

@lowe0292 you're right. On it.

[eashaw]

Hey @lowe0292, we've updated the error message.