mirrors/brew
1
0
Fork 0
mirror of https://github.com/Homebrew/brew.git synced 2025-07-14 16:09:03 +08:00
Code Issues Packages Projects Releases Wiki Activity

Remove dbm_test_read analytics.

Browse Source 
This can now be removed because my paranoia was unjustified and it's
successful 99.93% of the time.
This commit is contained in:
Mike McQuaid 2018-09-25 09:56:13 +01:00
parent 899bfbcaf1
commit 9a4b54f85d
No known key found for this signature in database
GPG Key ID: 48A898132FD8EE70
2 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
Library/Homebrew/cache_store.rb
View File

@ -97,7 +97,6 @@ class CacheStoreDatabase
end
false
end
Utils::Analytics.report_event("dbm_test_read", dbm_test_read_success.to_s)
cache_path.delete unless dbm_test_read_success
end
DBM.open(dbm_file_path, DATABASE_MODE, DBM::WRCREAT)

1
docs/Analytics.md
View File

@ -29,7 +29,6 @@ Homebrew's analytics records the following different events:
- an `event` hit type with the `install_on_request` event category and the Homebrew formula from a non-private GitHub tap you have requested to install (e.g. explicitly named it with a `brew install`) plus options and an event label as above. This allows us to differentiate the formulae that users intend to install from those pulled in as dependencies.
- an `event` hit type with the `cask_install` event category and the Homebrew cask from a non-private GitHub tap you install as the action and an event label as above. This allows us to identify the casks that need fixing and where more easily.
- an `event` hit type with the `BuildError` event category and the Homebrew formula that failed to install, e.g. `wget` as the action and an event label e.g. `macOS 10.12`.
- an `event` hit type with the `dbm_test_read` event category and `true` or `false` as the action (depending on if a corrupt DBM database was detected) and an event label e.g. `macOS 10.12`.
You can also view all the information that is sent by Homebrew's analytics by setting `HOMEBREW_ANALYTICS_DEBUG=1` in your environment. Please note this will also stop any analytics from being sent.