-
Notifications
You must be signed in to change notification settings - Fork 157
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
krr --install-completion crash #57
Comments
Hi there! Seems it's the same issue as described here: fastapi/typer#54. |
You can publish a package resulting from $ poetry build
$ sha256 dist/robusta_krr-1.3.2.dev0.tar.gz The Formula's file will look like that: class Krr < Formula
include Language::Python::Virtualenv
desc "Kubernetes Resource Recommender by Robusta"
homepage "https://github.com/robusta-dev/krr"
url "https://github.com/ganievs/krr/releases/download/test-homebrew/robusta_krr-1.3.2.dev0.tar.gz"
version "1.3.2"
sha256 "75850810d5083ee761662511e0ceefe99e2fad43feae8e53cd393c40e833bf21"
depends_on "[email protected]"
def install
virtualenv_install_with_resources
end
test do
system bin/"krr", "version"
end
end I did some tests on my fork and it works well on both Mac and Linux. |
The only issue is that we are building a standalone with pyinstaller to avoid potential dependancy issues The only think is I am a bit afraid on introducing such a big change for fixing a small problem with I will come back to this issue in the future after more important stuff is fixed and I will implement your solution. Thanks again |
Sure, No worries!
I just wanted to highlight the current packaging way might produce some similar bugs |
I'm currently having this same issue with version 1.6.0 installing it from homebrew |
Hi! Could you check whether fastapi/typer#237 solves this issue for you? |
Describe the bug
krr --install-completion
crashes when krr was install via homebrewTo Reproduce
Steps to reproduce the behavior:
Expected behavior
Shell completion installed successfuly
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: