When updating matchup data the process stops at different times and never completes (no success message is shown). The process stops at different weeks but usually within in the 2018 season of a 5+ year season league.
I have run this several times on two different machines (Windows) and the same issue occurs over and over.
I have deleted the extension and re-installed. I have deleted the DB and re-run several times. I have also downgraded chrome.
After the update process freezes I can close the popup and re open the popup and generate leader boards and record books. However the data is wrong. If I rerun the update process the data different but still wrong.
Digging into the chrome extensions errors using developer mode I have found the following 2 errors, I'm not sure if relevant.
Error 1
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
Refused to execute inline event handler because it violates the following Content Security Policy directive: "script-src 'self' blob: filesystem: chrome-extension-resource:". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution.
When updating matchup data the process stops at different times and never completes (no success message is shown). The process stops at different weeks but usually within in the 2018 season of a 5+ year season league.
I have run this several times on two different machines (Windows) and the same issue occurs over and over.
I have deleted the extension and re-installed. I have deleted the DB and re-run several times. I have also downgraded chrome.
After the update process freezes I can close the popup and re open the popup and generate leader boards and record books. However the data is wrong. If I rerun the update process the data different but still wrong.
Digging into the chrome extensions errors using developer mode I have found the following 2 errors, I'm not sure if relevant.
Error 1
Error 2