-
Notifications
You must be signed in to change notification settings - Fork 974
Improve handling of switching dat file versions #8489
Comments
@mrose17 try clearing your .dat files. I think this is a symptom of switching between dev-channel and master frequently. Let's leave this open though so I can improve that use case. Basically though your session stores the downloaded adblock version and then it's not actually that version. |
deleting the |
what?!? i don't have to reinstall either node or the OS?... (-; the only step i was missing was the |
actually I just thought of the reason I think you guys got this. i) install node_modules on master you get ad-block library which expects data files in format v3. The opposite can happen too if you got he other way. The way to fix this is to have the library specify the dat file version instead of having it separately defined in front end code. |
that makes sense. in this case, the culprit was |
This adds a new argument version, which if undefined it uses the old way to get it. We only currently specify a version explicitly from the ad-block lib, otherwise we use the front-end config. The lib knows best which version it is on. In this repo we had problems because people switch between branches but don't npm install again. With a fully C++ implementation this wouldn't have been seen. Related: brave-experiments/ad-block@85e6b35 Fix #8489 Auditors: @SergeyZhukovsky
Did you search for similar issues before submitting this one? yes
Describe the issue you encountered: go to a site from the about:preference# payments page
Platform (Win7, 8, 10? macOS? Linux distro?): macOS
Brave Version (revision SHA): 6638b91
Steps to reproduce:
npm run watch
&npm start
Actual result: crash
Expected result: new tab with website
Will the steps above reproduce in a fresh profile? If not what other info can be added?
Is this an issue in the currently released version? it's in master & dev-channel
Can this issue be consistently reproduced? yes
Extra QA steps: none
Screenshot if needed:
Any related issues: none
The text was updated successfully, but these errors were encountered: