I created this new app:
The app works great upon first deployment and keeps working for a while then starts timing out seemingly randomly. I suspect it may be either too unstable (it's using the new 'querychat' package GitHub - posit-dev/querychat <shout out to Joe & Carson!>) or perhaps it is resource constrained in the free tier? I don't see any hints in the log so I was hoping you might have some ideas on why it starts timing out.
Thanks!
Hi Drew,
Could you please describe (or screenshot) what the timeout looks like? Thanks,
Alex
Hi Alex,
It just sits at a load screen (see attached image). There is no load screen if I republish it. It does take a while to publish initially with all the dependencies of the 'querychat' package but it loads near instantly and performs very well as soon as it is published until it eventually exhibits this stalling behavior.
Thanks!
Interesting. I'll mark it to investigate when we are back on Monday. Thanks for sharing.
Hi Drew,
It looks like you are installing DuckDB from a GH repo.
If that is true, we might be hitting memory issues on subsequent republishes as it is a very large package and we don't yet cache R packages that are installed from GH.
Installing the package from CRAN or from https://packagemanager.posit.co/ should help if that is in fact the issue. Is your project able to do that?
Best,
Alex
Thanks Alex, I suspect you're right. DuckDB is installed during the querychat package installation from GH as a dependency.
Hi Alex,
I pointed the duckdb manifest.json reference to CRAN instead of the default GH location referenced by the querychat package. Looks like that did the trick!
Thanks Again!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
If you have a query related to it or one of the replies, start a new topic and refer back with a link.
