rstudio / rsconnect

Publish Shiny Applications, RMarkdown Documents, Jupyter Notebooks, Plumber APIs, and more
http://rstudio.github.io/rsconnect/
133 stars 82 forks source link

Multiple accounts created for one account #1103

Open gaborcsardi opened 3 weeks ago

gaborcsardi commented 3 weeks ago

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?

aronatkins commented 3 days ago

@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 https://github.com/rstudio/rsconnect/issues/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.

gaborcsardi commented 3 days ago

Yep, they both look recent:

❯ find . -name "*.dcf" | xargs ls -l
-rw-r--r--@ 1 gaborcsardi  staff  283 Oct  4 08:45 ./rsconnect/colorado.posit.co/gabor/quarto-stock-report-r.dcf
-rw-r--r--@ 1 gaborcsardi  staff  362 Oct  8 11:13 ./rsconnect/documents/index.qmd/colorado.posit.co/gabor/quarto-stock-report-r.dcf

appId is the same for both. Is this normal?

Nevertheless deployment works now, even though I didn't do anything, so it was probably something with colorado.