Missing block errors trying to import DB from v7.6.0 to v7.11.2

[morninglite]

This is using the included Dockerfile in augur-node@v7.11.2, with the only modification being to copy in the augur-1-4.db file from the older node.

These errors occur at the end of the migration process, after the expected SQLite errors (no such column: bestBidTakerInvalidProfitTokens).

2019-10-01T19:35:17.132924311Z Starting websocket server on port 9001
2019-10-01T19:35:17.901957174Z Getting Augur logs from block 8614387 to block 8658354
2019-10-01T19:35:17.903084218Z Block range 8614387 to 8658354 exceeds currentBlock 8658346
2019-10-01T19:35:17.919281678Z Error: Block range 8614387 to 8658354 exceeds currentBlock 8658346
2019-10-01T19:35:17.919301947Z     at Object.getAllAugurLogs (/app/node_modules/augur.js/src/events/get-all-augur-logs.js:37:26)
2019-10-01T19:35:17.919315483Z     at downloadAugurLogs (/app/src/blockchain/download-augur-logs.ts:84:16)
2019-10-01T19:35:17.919318025Z     at Promise (internal/util.js:275:30)
2019-10-01T19:35:17.919320476Z     at new Promise (<anonymous>)
2019-10-01T19:35:17.919323170Z     at downloadAugurLogs (internal/util.js:274:12)
2019-10-01T19:35:17.919326031Z     at Object.<anonymous> (/app/src/blockchain/bulk-sync-augur-node-with-blockchain.ts:57:37)
2019-10-01T19:35:17.919328954Z     at Generator.next (<anonymous>)
2019-10-01T19:35:17.919331432Z     at fulfilled (/app/src/blockchain/bulk-sync-augur-node-with-blockchain.ts:4:58)
2019-10-01T19:35:17.919333956Z     at process._tickCallback (internal/process/next_tick.js:68:7)
2019-10-01T19:35:17.919458941Z Stopping Augur Node Server

This occurs reliably, and apparently regardless of the block height the imported DB is at. Meaning, if I now start the old v7.6.0 version with the same DB, it syncs as normal without any errors. I then stop it and copy this updated DB to the new v7.11.2 node, where the same error occurs but with the newer block height:

2019-10-01T19:39:00.683575034Z Getting Augur logs from block 8657928 to block 8658382
2019-10-01T19:39:00.684734591Z Block range 8657928 to 8658382 exceeds currentBlock 8658367
2019-10-01T19:39:00.701041529Z Error: Block range 8657928 to 8658382 exceeds currentBlock 8658367
2019-10-01T19:39:00.701059524Z     at Object.getAllAugurLogs (/app/node_modules/augur.js/src/events/get-all-augur-logs.js:37:26)

Upon restart, the node seems to sync a few more blocks without reporting any errors, but dies shortly thereafter without any exception or error message:

2019-10-01T19:39:31.132534956Z got 118 logs in blocks { fromBlock: 8657986, toBlock: 8658387 }
2019-10-01T19:39:31.146640325Z Fetching blocks details from 8658023 to 8658322
2019-10-01T19:39:31.539831356Z Fetched 10 / 22 block details (current: 8658207)
2019-10-01T19:39:31.805998229Z Fetched 20 / 22 block details (current: 8658276)
2019-10-01T19:39:31.881425627Z npm ERR! code ELIFECYCLE
2019-10-01T19:39:31.881686445Z npm ERR! errno 1
2019-10-01T19:39:31.882330523Z npm ERR! augur-node@7.11.2 start: `ts-node ./src/runServer`
2019-10-01T19:39:31.882376440Z npm ERR! Exit status 1
2019-10-01T19:39:31.882470920Z npm ERR! 
2019-10-01T19:39:31.882520771Z npm ERR! Failed at the augur-node@7.11.2 start script.
2019-10-01T19:39:31.882586672Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Obviously, there's the workaround of just syncing from scratch with v7.11.2, which I am doing now. But, I still thought this was worth reporting.