You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(git-annex)hopa:~/proj[master]brainlife
$> bl dataset download --id 5a065cc75ab38300be518f51
(node:22532) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Couldn't find your access token. Please try logging in by running 'bl login'(node:22532) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.$> bl loginusername: ...
while I can click "download" on brainlife web ui and then agree to HCP terms and proceed
The text was updated successfully, but these errors were encountered:
Yes, at the moment, our command line interface requires our users to authenticate - even though they might be downloading publically downloadable datasets.
It's really simple to sign up to Brainlife, so at the moment this is somewhat considered to be a "feature" that allows us to do better auditing (to know who is doing the download).. but I understand that it's inconsistent.
I was trying to get
https://brainlife.io/pub/5a0f0fad2c214c9ba8624376#5a065cc75ab38300be518f51
while I can click "download" on brainlife web ui and then agree to HCP terms and proceed
The text was updated successfully, but these errors were encountered: