New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] #47
Comments
Hi @alvelda, just to get a better understanding of your problem, you used Brew to install the package and are unable to run the |
Yes, that’s correct.
… On Aug 1, 2022, at 8:40 PM, Andrew Hossack ***@***.***> wrote:
Hi @alvelda <https://github.com/alvelda>, just to get a better understanding of your problem, you used Brew to install the package and are unable to run the dashtools command?
—
Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANRS4Q3F6F4CK22K3JF2Z3VXCKDLANCNFSM55GKP6OQ>.
You are receiving this because you were mentioned.
|
@alvelda, try uninstalling and re-installing directly from pip:
Pip handles the CLI entry point when it is installed. I'm not sure how Brew works to install pip packages. Let me know what you find and I can update the docs. |
Okay, that worked, but now I get " Invalid Heroku App name whether I create one or use one of the default random names. |
@alvelda thanks for providing that feedback. Looks like Heroku changed how their sever responds to unavailable app names behind the scenes. I've pushed out an update for Version 1.7.3 so go ahead and run:
Let me know if this helps! |
Thank you so much for helping improve the quality of dash-tools!
We do our best to catch bugs during the release process, but we rely on your help to find the ones that slip through.
Describe your context
Please provide us your environment, so we can easily reproduce the issue.
dash-tools --version
belowDescribe the bug
Brew installer doesn't set up path variable, not clear where executable is to invoke the dash-tools command is so as to add it to the Path.
installed a file tree at
/Users/alvelda/anaconda/envs/python38/lib/python3.8/site-packages
where's the executable?
Expected behavior
A clear and concise description of what you expected to happen.
I would have expected the path variable to be updated by the installation script.
If applicable, add screenshots or screen recording to help explain your problem.
The text was updated successfully, but these errors were encountered: