-
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
KeyError: 'id' when deploying jupyter notebook #523
Comments
I attempted to reproduce this by assigning CONNECT_SERVER and CONNECT_API_KEY to values but we still use the stored credentials as expected. I suspect we're calling out to Connect to get an App ID but Connect isn't able to return one for whatever reason. I haven't been able to reproduce though. I tried a Connect server...
All scenarios throw the expected errors. I think we'll need to get some Connect logs and try to find out if a Connect app_id was ever created on their server. |
Hey y'all, thanks for looking in on my problem. Maybe this will be useful...I went into rsconnect-python's 'api.py' code on my local machine and added a couple print statements:
The output is like so:
You can see there is no "id" key. 'applications' looks like an up-to-date list of the things we've published to our connect server, so it appears to be connecting properly to the server at least. |
Good idea, I tried the same and I get back:
I've been following your ticket with support. Can you try I noticed when you sent the output of |
Ahh, would you look at that, it worked! |
Though looking back, I think the lack of quotes in the URL was an Outlook thing - it "helpfully" replaced the URL with a link. In the actual servers.json file the quotes are there. |
Great! Any idea how you added that server to get the |
Sorry, I missed your previous response. If you re-add the server does it continue to work? |
Ahh, to you first question - I assume I used
since that is in my zsh history. I remade the server with |
Can you remove the slashes at the end of the url? I tried a double slash with my test server but it continued to work.
If removing the slashes doesn't help, for the time-being remove the server and continue to use the |
We also added a
Give that a shot and send us the output either here, or in the support ticket you have opened. |
Followed up through support email - in summary: I'm now unblocked, but the '//' at the end of the url is causing the issue for as-yet-unknown reasons. |
We have a report of a keyerror when deploying a jupyter notebook.
After doing some code reading, it's unclear to me how this could occur if we get a successful response from
self.app_create
https://github.com/rstudio/rsconnect-python/blob/b583723fbc0157f2ed83d8501aeaadb9baa51f06/rsconnect/api.py#L253-L257
We'll follow up with additional diagnostic information but I thought we should file an issue here in case others have run into this problem.
rsconnect deploy notebook -v ./snowflake_pythonconnector_demo.ipynb
Is it possible there's 2 api keys in play as a result of the environment var being different than the api key from the cache?
The text was updated successfully, but these errors were encountered: