Error on deploy to "unable to satisfy package: elmer (0.0.0.9000)"

I am trying to deploy a simple app to ShinyApps.io, but I keep getting an error with the elmo package.

The complete error is:

Fejl: Unhandled Exception: child_task=1486761914 child_task_status=failed: Error building image: Error fetching elmer (0.0.0.9000) source. unable to satisfy package: elmer (0.0.0.9000)

Reprex:

library(shiny)
library(shinychat)

ui <- bslib::page_fluid(
  chat_ui("chat")
)

server <- function(input, output, session) {
  chat <- elmer::chat_openai(system_prompt = "You're a trickster who answers in riddles")
  
  observeEvent(input$chat_user_input, {
    stream <- chat$stream_async(input$chat_user_input)
    chat_append("chat", stream)
  })
}

shinyApp(ui, server)

I have tried many different versions of my DESCRIPTION file. The latest iteration, which uses remotes, is pasted below. I have also tried pak and renv, but I keep getting the same error.

chatGPT, Claude, Shiny assistant couldn't help either.

All help is appreciated.

Package: myshinyapp
Title: My Shiny App
Version: 0.1.0
Author: Steen Harsted <sharsted@health.sdu.dk>
Description: A Shiny app that plays a chiro patient
Depends: 
    R (>= 3.5.0)
Imports:
    shiny (>= 1.7.0),
    shinychat,
    elmer,
    bslib (>= 0.5.0)
Remotes:
    github::tidyverse/elmer@main,
    github::jcheng5/shinychat@main
Encoding: UTF-8

I'm getting the same error. I also tried the example here: LLM Workshop – Interfacing with large language models

A couple of weeks ago I opened a github issue because httr2 was generating the same error message. The reply was that once the CRAN version of the package was updated the error would resolve. My guess is that the elmer developers are not really considering shinyapps.io deployment.

1 Like

There have been a lot of issues deploying packages from GH recently. This is what fixed things for me: Unable to deploy to shinyapps.io due to package dependency - #5 by jchou so you might want to try that (including the private repo flag). That may still not work for you though as they are not your repos, but you could consider forking and installing your fork instead of the main repo.

1 Like

Please see the following message, which confirms the issue is due to GitHub rate limiting and the temporary workaround:

Best,
Randy

Following info from the linked issue, if I select "Private repo access also enabled" then I am able to successfully deploy.

2 Likes