Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Re-enable DAU and MAU stats on Linux #7562

Closed
bbondy opened this issue Mar 8, 2017 · 8 comments
Closed

Re-enable DAU and MAU stats on Linux #7562

bbondy opened this issue Mar 8, 2017 · 8 comments

Comments

@bbondy
Copy link
Member

bbondy commented Mar 8, 2017

Test plan

#7651 (comment)


We should still do an update check, but change the messaging of the toolbar. Since 0.12.1 we aren't getting new update pings unless the user checks manually:
dcc4a8f

@bbondy bbondy added this to the 0.13.6 milestone Mar 8, 2017
@bbondy
Copy link
Member Author

bbondy commented Mar 8, 2017

@aekeus if you want a break from addfunds I'd appreciate the help on this one

@bbondy
Copy link
Member Author

bbondy commented Mar 8, 2017

Keeping in mind if this was a crash we don't want to re-introduce it:
#3907

@aekeus
Copy link
Member

aekeus commented Mar 8, 2017

Ok, thanks. Will do.

@aekeus aekeus self-assigned this Mar 8, 2017
@aekeus
Copy link
Member

aekeus commented Mar 10, 2017

I am going to break this up to two issues. The first will be re-enabling the ping to the updater service. The second will be the notification in the update bar that a new version is available.

aekeus added a commit that referenced this issue Mar 10, 2017
This change re-enables the update check, used to send anonymous stats, for Linux.

The update check does not show the update bar, even if there is a newer version
of the software available. This will be addressed in a later commit.

Testing:

Testing this change from a QA perspective is problematic. These are the steps
I used to test the functionality of the change.

A)

  * Change the version in package.json to a previous release version
  * Build the binary on Linux
  * Launch the browser ensuring:
    * The browser does not crash on update init
    * The updater scheduler is initiated
    * Metadata is retrieved from the updater
    * The updater bar is NOT shown
    * The browser does not crash
    * No attempt is made to update the browser binary

B)

  * Change the browser version in package.json to a non-existent version
  * Build on Linux and launch
  * Ensure no metadata is retrieved
  * Ensure that the ping is recorded in the dw.fc_usage table of stats

Auditors: @bbondy

Implements: #7562
@luixxiul
Copy link
Contributor

@aekeus is it OK to close this thanks to #7651?

@aekeus
Copy link
Member

aekeus commented Mar 12, 2017

@luixxiul yes, this issue is fixed with pull request #7651

@alexwykoff
Copy link
Contributor

@aekeus I tried setting version to 0.13.3 in package.json and found the following after launch:

brave@0.13.3 start /home/test/Development/browser-laptop
node ./tools/start.js --user-data-dir=brave-development --debug=5858 --enable-logging --v=0 --enable-extension-activity-logging --enable-sandbox-logging --enable-dcheck

Crash reporting enabled
{ version: '0.13.5',
name: 'Brave 0.13.5',
pub_date: '2017-03-03T21:39:47.551Z',
notes: 'Added sync between computers, suppressible per-tab alert and confirm message dialogs, preference page for plugins, fixed wallet recovery, and fixed various UI issues. More details: https://github.com/brave/browser-laptop/releases/tag/v0.13.5dev\n\nHotfix for a crash which could happen when loading an invalid URL. More details: https://github.com/brave/browser-laptop/releases/tag/v0.13.4dev',
url: 'https://brave-download.global.ssl.fastly.net/multi-channel/releases/dev/0.13.5/linux64/Brave.tar.bz2' }

So it appears to be contacting the update server which the PR said should not be happening.

This was on SHA : 77c562c

@aekeus
Copy link
Member

aekeus commented Mar 16, 2017

That is the correct behaviour. We need to contact the update server to record the statistic (the metadata is retrieved as a no-op side effect).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.