Closed joaoleveiga closed 4 years ago
A few notes:
Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | ||
---|---|---|---|---|---|
src/services/Corona.js | 0 | 1 | 0.0% | ||
src/api/Corona.js | 4 | 19 | 21.05% | ||
<!-- | Total: | 5 | 21 | 23.81% | --> |
Files with Coverage Reduction | New Missed Lines | % | ||
---|---|---|---|---|
src/services/Corona.js | 1 | 15.07% | ||
<!-- | Total: | 1 | --> |
Totals | |
---|---|
Change from base Build 488: | -0.4% |
Covered Lines: | 470 |
Relevant Lines: | 763 |
A few notes:
If you prefer, the algorithm can be changed to sha256 instead of md5. I don't have any preference in the algorithm, so, if you decided to use md5, I think there's no need to change algorithm to sha256.
I still didn't do the migration script to update the checksums of reports alread present in the database. I'll try to figure that out tomorrow. Ok, no problem! I'll wait for the script to merge PR into
master
.
@miguelcarreiro Whenever you can, can you please take a look at the migration file? I think I have probably tried 5 different approaches already and I still can't seem to understand how can I update the rows.
What's happening is that when I run the migration, it correctly fetches all the reports, and their md5sum, and tries to update. However, when committing the transaction (I think), only the last md5sum is used for all the rows :sob:
Updating the PR, as per our discussion on Discord about dropping the migration bit that updates the data.
Description
This pull request addresses issue BOT-161.
Task items:
md5sum
field; ~Added migration to fill in this field if the database has previous reports;~eslint --fix ./src