(Update: there are some things in here that are actually bugs - 3 and 4)
About basic usage metrics:
flox collects basic usage metrics in order to improve the user experience,
including a record of the subcommand invoked along with a unique token.
It does not collect any personal information.
Do you consent to the collection of basic usage metrics? (Y/n)
I’ve answered no to this question, because it’s not clear what a record of the subcommand invoked means and how this data is being used. Some examples of what’s not being tracked and what is would help me to chose yes.
No fish support
I’m using fish as my default shell, but was greeted with this:
Thanks so much for your patience … version 0.0.7-r82 is now available for download and should address issues #3 and #4 above. Rest assured we will be circling back to respond to the first two issues as well but I wanted to let you know right away that we’ve rolled out this new version.
UPDATE: found another bug, version 0.0.7-r83 is now the latest version, osx, deb and rpm downloaders are available for download.
(@etorreborre - if you’d prefer to activate the new version without a reinstall you can access it from the flox/default environment per usual.)
We have two mechanisms for providing secure access to these private repositories during the closed beta - one for curl and one for git - but yes after the closed beta we’ll be marking this repository as public.
Just to confirm, fish support is on our list of enhancements to get done. Once implemented, it will be in the release notes in an upcoming release. I don’t currently have a timeframe for this unfortunately but I can say it is definitely something we want to get done and I’ve added you to the list of people requesting it
Thank you for this very valuable input. I have logged ticket to get this wording improved and to include examples as you suggest.
To answer the question itself, the flox CLI will batch up the count of the various subcommand invocations and only send batches at most once in an hour in a single curl invocation. The metric counts are accumulated in ~/.cache/flox/metrics-events.json by default if you want to have a look.
Thanks for fixing these so quickly. I’m not expecting bugs to get fixed in the weekend
One small thing I notice:
flox install ripgrep
warning: You appear to have cloned an empty repository.
flox remove ripgrep
warning: remote HEAD refers to nonexistent ref, unable to checkout
It seems to work, but I’m not sure where the warnings about the repo come from?
Hi @paulovieira - I just wanted to let you know we’re still discussing potential fixes for the issue you cited with the hello-python example and we’re planning to get a fix out later today. Thanks for being patient with us!
just a quick update regarding point 1) at the top of this thread about collecting basic usage metrics. We have now added an example as suggested to help clarify what data could be collected.
Thanks for the suggestion!