Error syncing market data after update to 1.6.1
See original GitHub issueAfter the update to 1.6.1 I am getting the following error when attempting to sync market data:
insert into `token_supply` (`supply`, `token`) select '0' as `supply`, '0xf4b0d6d4926d69a40bff3251ae3cbd8cc092b6b4' as `token` union all select '0' as `supply`, '0x82f0a32ab18a3be686e059316eb5139c422775fe' as `token` - SQLITE_CONSTRAINT: UNIQUE constraint failed: token_supply.token
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (2 by maintainers)
Top Results From Across the Web
blaize-tech/bitwin24-explorer: An open source block ... - GitHub
The market database only supports (& defaults to) reindex mode. * If check mode finds missing data(ignoring new data since last sync), index_timeout...
Read more >Error reference | Anthos Config Management - Google Cloud
The ID of InternalError changed to KNV9998 with Config Sync 1.6.1. ... This command returns a stream of the state of the resource...
Read more >Changelog | WP Fusion
Fixed SQL error when searching for The Events Calendar events that are protected by tags, when Filter Queries was set to Advanced mode;...
Read more >"Module was compiled with an incompatible version of Kotlin ...
I was able to resolve it by updating Gradle from 6.7.1 to 6.9 (or any other version). Just go to gradle-wrapper.properties and change...
Read more >Update Ledger Nano S firmware
Installing the firmware update. Depending on the firmware version currently installed on your device, select one of the following procedures:.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing this issue, as the DB reset bug should be fixed when version 1.7.0 is released.
Thanks, renaming the “augur” folder forced a reset, and now 1.6.2 now works for me.