Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to exclude sites from the a-c table #2943

Closed
kjozwiak opened this issue Jan 14, 2019 · 18 comments · Fixed by brave/brave-core#1760
Closed

unable to exclude sites from the a-c table #2943

kjozwiak opened this issue Jan 14, 2019 · 18 comments · Fixed by brave/brave-core#1760
Assignees
Labels
bug feature/rewards needs-investigation A bug not 100% confirmed/fixed priority/P2 A bad problem. We might uplift this to the next planned release. QA Pass-Linux QA Pass-macOS QA Pass-Win64 QA/Yes release-notes/include

Comments

@kjozwiak
Copy link
Member

Description

We're still getting reports from the community that even after #1693 being released in 0.58.21 which was the hotfx 3, users are still having issues excluding websites from the a-c.

Steps to Reproduce

N/A... We currently don't really have any STR. We should try working with some users that are experiencing this to see if we can either get their profiles or see if they're receiving an errors in the browser console.

Actual result:

Users can't exclude websites from the a-c table under Rewards.

Expected result:

Users should be able to exclude publishers from the a-c table under Rewards

Reproduces how often:

I'm not sure as we don't really have STR yet.

Brave version (brave://version info)

Brave 0.58.21 Chromium: 71.0.3578.98 (Official Build) (64-bit)
Revision 15234034d19b85dcd9a03b164ae89d04145d8368-refs/branch-heads/3578@{#897}

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds?

I'm not sure as we don't really have STR yet. We'll need more information from the users that are still experiencing this issue.

Additional Information

CCing @brave/legacy_qa @NejcZdovc

@kjozwiak kjozwiak added this to the 1.x Backlog milestone Jan 14, 2019
@kjozwiak
Copy link
Member Author

We fixed one of the cases in #1693 but it appears that some users are still experiencing this issue.

@glawrence
Copy link

I have "Version 0.58.21 Chromium 71.0.3578.98 (Official Build) (64-bit)" on "mac OS Mojave 10.14.2" and still see this problem. However some sites I can exclude, others I can't, it seems that the recently added ones can be removed, not older ones. Also my "Next contribution date" is still on 18/11/2018, which suggests another problem

@kjozwiak
Copy link
Member Author

@glawrence when you attempt to exclude websites from the auto-contribution table, do you see an errors in the browser console when clicking on the X to exclude?

@GeetaSarvadnya
Copy link

@glawrence
Copy link

No, nothing

@MrRobboto
Copy link

@kjozwiak

To provide what I'm experiencing:

I'm noticing the same behavior people are reporting still happening in 0.58.21. After messing around with it though, I see now the behavior is latency, not complete failure.

If you just click around, it looks like nothing is happening but if you wait a few seconds you'll see it works. There's just very bad latency and no spinner to show the user something is happening in the background.

I have no console errors and consistently I can hit the "X" next to these and it works - but it takes a varying amount of time to work. Some sites it's instant, some sites it takes nearly 10 seconds to work. It's averaging around 3-4 seconds for me on ~100mbps up/down.

Hope this helps...

@scmart
Copy link

scmart commented Jan 14, 2019

@kjozwiak I also see the latency issue, but that is seperate from the issue of not being able to exclude most sites, or having sites show up twice.

Also, I'm seeing no errors in console attempting to remove sites.

@LaurenWags
Copy link
Member

I wonder if sites showing up twice is due to this issue #2911

@MrRobboto
Copy link

@scmart is there a reason you believe these are separate?

The latency I'm seeing varies depending on the site you are trying to exclude so my point was that even though people are reporting they "can't exclude some sites", that very well could be the latency issue still and they either aren't waiting long enough to see it or the latency could possibly be so bad for some sites it times out. There are several plausible ways these behaviors could be related to the same issue so with the information we have I would be hesitant to say they are separate...

@MrRobboto
Copy link

MrRobboto commented Jan 15, 2019

@LaurenWags looks plausible! In any case, the showing up twice seems unrelated to this issue. I tested the latency issue quite a bit and all the sites I tried to exclude worked perfectly fine and the UI updated perfectly as you'd expect (no double entries for me) - just really bad latency, 10+ seconds on some, not as bad on others. I could imagine it timing out on some sites causing it to fail completely for some people but I did not observe this...

@scmart
Copy link

scmart commented Jan 15, 2019

@MrRobboto No, it's separate. It's not latency, it's just an inefficient sorting algorithm I assume (its all local, no network use).

@MrRobboto
Copy link

MrRobboto commented Jan 15, 2019

@scmart so your reason is because you have an assumption that there's a sorting algorithm, and it's inefficient? It's just a list sorted by percentage, updating the DOM after excluding is stupid simple. This doesn't seem to be UI or JS related, it's on the C++ side and there is async processing (background) causing latency. I'm not sure if it's local or if any network comm is required, you would need to be more familiar with the code base to know that (I'm guessing you are not).

When they fixed the bug with the JS exclude list not being initialized #1693, you can see they check it now in the new release and then it uses a message callback to invoke code on the C++ side. That then appears to be interacting with a bat ledger. I don't know if that is some local ledger or what but I don't think you would see network comm on that side in chrome dev tools, this is under-the-hood stuff - although I do not know for sure.

So I'll admit I'm speculating and not familiar with the code but I did take the time to look at it and tried to come up with a more reasonable hypothesis for why people are still reporting this. I thought the same exact thing as everyone else. I thought it just wasn't working for weeks (and it really wasn't before) but now it appears it's a delay, whether network latency, or just slow async processing (still considered latency btw).

@MrRobboto
Copy link

MrRobboto commented Jan 17, 2019

@Brave-Matt @kjozwiak

Just an update on my observations - I was just playing around with this more and stepping through the code when I noticed there does seem to be a problem excluding sub-domains when you have already excluded the domain. This does appear to be separate from the latency issue I'm also seeing.

My guess is this is from the check on publisherKey, instead of url:

if (!state.excluded.includes(publisherKey)) {  
    chrome.send('brave_rewards.excludePublisher', [publisherKey])  
    state.excluded.push(publisherKey)  
    state = {  
        ...state,  
        excluded: state.excluded  
    }  
}

For instance - I took a look at the exclude list as it's saved to localStorage and I see it's just publisherKey, which is only the main domain. At some point I excluded google.com successfully but in my a-c list I have mail.google.com showing up as just "google.com" (twice, different bug). So that check I'm guessing fails since it only checks the publisher key which looks to be the same across subdomains...

Top of A-C list in localStorage:
image

Exclude list in localStorage:
image

Top of my A-C Table:
image

@rebron rebron added the priority/P2 A bad problem. We might uplift this to the next planned release. label Jan 18, 2019
@NejcZdovc NejcZdovc self-assigned this Jan 20, 2019
@eljuno
Copy link

eljuno commented Feb 2, 2019

@rebron rebron removed this from the 1.x Backlog milestone Feb 7, 2019
@scmart
Copy link

scmart commented Feb 23, 2019

This seems to be finally working correctly for me.

@MJae
Copy link

MJae commented Mar 5, 2019

Still experiencing the issue. Using Version 0.60.47 Chromium: 72.0.3626.119 (Official Build) (64-bit)

@LaurenWags
Copy link
Member

LaurenWags commented Mar 20, 2019

Verified passed with

Brave 0.63.14 Chromium: 73.0.3683.75 (Official Build) dev(64-bit)
Revision 909ee014fcea6828f9a610e6716145bc0b3ebf4a-refs/branch-heads/3683@{#803}
OS Mac OS X

Verification passed on

Brave 0.63.14 Chromium: 73.0.3683.75 (Official Build) dev (64-bit)
Revision 909ee014fcea6828f9a610e6716145bc0b3ebf4a-refs/branch-heads/3683@{#803}
OS Windows 10 OS Build 17134.523

Used test plan from brave/brave-core#1760
Also tested excluding and including of site in a-c table

Verification passed on

Brave 0.63.15 Chromium: 73.0.3683.75 (Official Build) dev (64-bit)
Revision 909ee014fcea6828f9a610e6716145bc0b3ebf4a-refs/branch-heads/3683@{#803}
OS Linux

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug feature/rewards needs-investigation A bug not 100% confirmed/fixed priority/P2 A bad problem. We might uplift this to the next planned release. QA Pass-Linux QA Pass-macOS QA Pass-Win64 QA/Yes release-notes/include
Projects
None yet
Development

Successfully merging a pull request may close this issue.