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
I realize this is hard to reproduce. :( I tried to deploy the example stock app from RStudio a couple of times, stopped the deployment after ~15 minutes, it was stuck at determining session server location, then tried to call rsconnect::deployApp() from the console, that's stuck as well.
Now I have a state where seemingly I have multiple deployments:
> rsconnect::deployApp()
── Preparing for deployment ──────────────────────────────────────────────────────────────────────────
This directory has been previously deployed in multiple places.
Which deployment do you want to use?
1: quarto-stock-report-r (server: <server>.posit.co / username: gabor):
<https://<server>.posit.co/rsc/content/<uuid>/>
2: quarto-stock-report-r (server: <server>.posit.co / username: gabor):
<https://<server>.posit.co/rsc/content/<uuid>/>
Is this expected? Maybe rsconnect could detect that these are the same and offer some advice?
The text was updated successfully, but these errors were encountered:
@gaborcsardi - Do you know if those deployment records were created recently? Double entries are unexpected. Could you see what is in the corresponding *.dcf file (under the rsconnect directory)?
We resolved #1017 in rsconnect-1.2.0. Prior to that version, rsconnect might create duplicate records for Quarto content. I don't know of any automatic fix-up. You'll need to remove the duplication from the dcf file.
I realize this is hard to reproduce. :( I tried to deploy the example stock app from RStudio a couple of times, stopped the deployment after ~15 minutes, it was stuck at determining session server location, then tried to call
rsconnect::deployApp()
from the console, that's stuck as well.Now I have a state where seemingly I have multiple deployments:
Is this expected? Maybe rsconnect could detect that these are the same and offer some advice?
The text was updated successfully, but these errors were encountered: