Underhanded applies malice here rather than a bug. If you can reproduce this behaviour: please file an issue and I'll fix it.
Also, as stated before (and the data dump hopefully shows): this is anonymous information that's useful for us and the community to be able to prioritise our limited resources.
Well, I can't reproduce it now because I've already upgraded, and as far as I can tell there is no way to go backwards.
Its underhanded in the sense that there is no message to the user that this is occurring. I do understand your need for this feedback, but I do not think that home-brew should change this setting once the user has set it to "do not report". This is key to the adoption of homebrew in some environments - for example, on some corporate networks having automatic exfiltration of analytical data, anonymous or otherwise, is instant disqualification for installation - and I've already had that conversation with our sysadmins, who notice these things almost immediately.
If there is something I can do to help you debug this, let me know - otherwise I'll just happily continue upgrading home-brew as time goes by, and if I see something, I'll say something.
> but I do not think that home-brew should change this setting once the user has set it to "do not report"
We never intentionally do so and never have. Other than your comment we've not had any mention that this is the case. If you can find a way to reproduce this and file an issue, that'd be great and I'll do my best to fix it as soon as possible.
Also, as stated before (and the data dump hopefully shows): this is anonymous information that's useful for us and the community to be able to prioritise our limited resources.