Follow up of #3134
Pubs which are already in a-c table are getting deleted on upgraded profile after revisiting
when revisiting publishers that are already in the table, publishers are getting removed from a-c table.
pubs which are in a-c table should not get deleted after revisit
Easy
Brave | 0.59.32 Chromium: 72.0.3626.81聽(Official Build)聽(64-bit)
-- | --
Revision | ac8b982e05014492d1bd7d317628a4f22a97ffa0-refs/branch-heads/3626@{#796}
OS | Windows 10
@NejcZdovc @brave/legacy_qa
@GeetaSarvadnya can you please paste before and after ac table
@NejcZdovc Please find the below screen shots:
Before:
UI:

publisher_info_db:

After:
UI:

publisher_info_db:

Reproduced on 0.58.21 --> 0.59.32 update on macOS. Here are my publisher_info_db tables
0.58.21:

0.59.32 (after visiting a site to trigger recalculation):

Steps:
publisher_info_db to see negative scores.publisher_info_db still has negative scores.@LaurenWags Able to reproduce the above steps on Windows 10 x64
Negative scores are stores in a-c table when we relaunch and add few more sites to a-c table in 0.58.21

Additionally, if you follow these modified steps (no change to settings) you get % values which are off after updating to 0.59.32:
publisher_info_db (no negative scores)publisher_info_db still fine.0.58.21:

Update to 0.59.32 and visit DDG:

Verified passed with
Brave | 0.59.33 Chromium: 72.0.3626.81聽(Official Build)聽(64-bit)
-- | --
Revision | ac8b982e05014492d1bd7d317628a4f22a97ffa0-refs/branch-heads/3626@{#796}
OS | Mac OS X
publisher_info_db are accurate)publisher_info_db are accurate)Verification passed on
Brave | 0.59.33 Chromium: 72.0.3626.81聽(Official Build)聽(64-bit)
-- | --
Revision | ac8b982e05014492d1bd7d317628a4f22a97ffa0-refs/branch-heads/3626@{#796}
OS | Windows 10
publisher_info_db are accurate)publisher_info_db are accurate)Verified passed with
Brave | 0.59.33 Chromium: 72.0.3626.81聽(Official Build)聽(64-bit)
-- | --
Revision | ac8b982e05014492d1bd7d317628a4f22a97ffa0-refs/branch-heads/3626@{#796}
OS | Linux
publisher_info_db are accurate)publisher_info_db are accurate)Verified comments from (https://github.com/brave/brave-browser/issues/3162#issuecomment-458991004).
verified a profile from 0.58.21 with issues described in #3134 is updated to 0.59.33. Below are my observations
@NejcZdovc can you please look into the 1st point, which seems wrong to me, correct me if i am wrong.
@NejcZdovc please correct if wrong, but I think what @GeetaSarvadnya is seeing is expected because she has not yet visited any sites and the code to correct the a-c table (scores, % values, and weights) does not run until you visit a site. (also, we're not seeing any 0% items in the a-c table in 0.59.x due to https://github.com/brave/brave-browser/issues/2365)
@LaurenWags you are correct and this is expected
@NejcZdovc shouldn't the recalculations happen automatically upon upgrade which basically fixes the issue? We shouldn't wait until the user visits a site for the recalculation to happen with this fix. Could this be fixed for 0.60.x ?
@srirambv I think it doesn't matter as it will automatically be fixed when user do any action. So data will not be wrong for any operation that follows.