-
Notifications
You must be signed in to change notification settings - Fork 24
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
Error on pip warning message #270
Comments
I am also hitting this error message, even when supplying my own requirements.txt. Not an administrator on our installation, so this is now a blocker as I cannot deploy a new release of my code. I believe the solution is to set the environment variable |
@pfizzy, can you share your requirements.txt file and the error you're hitting? I was under the impression that it's only happening when giving Connect instructions to install pip, which shouldn't be needed. If pip is included in your requirements.txt file, you should be able to exclude that. |
Whoops, realized my error. I was attempting to move the build context into my source sub directory, because I had been compiling a fairly extensive list of The hitch is that I am running my deployment commands through a script which was capturing stderr and not stdout. The Connect build logs are routed to stderr, but the |
rsconnect-python 1.9.0
While testing the
--force-generate
flag which pulls all packages from the local environment to create a newrequirements.txt
file, I hit the following error:Command:
Error:
It seems pip is throwing a warning message about upgrading to the latest version but we're trying to include that line of output as an option when installing pip on Connect.
When upgrading to pip 22.2 locally, the deployment succeeded.
Full Logs
The text was updated successfully, but these errors were encountered: