Fixes timeouts for Mage

Signed-off-by: Mihovil Ilakovac <[email protected]>

wasp-ai/Dockerfile

@@ -33,7 +33,7 @@ RUN cd server && PRISMA_CLIENT_OUTPUT_DIR=../server/node_modules/.prisma/client/
 RUN cd server && npm run build
 
 FROM base AS server-production
-RUN curl -sSL https://get.wasp-lang.dev/installer.sh | sh -s -- -v 0.11.1-wasp-ai-11
+RUN curl -sSL https://get.wasp-lang.dev/installer.sh | sh -s -- -v 0.11.1-wasp-ai-12
 ENV PATH "$PATH:/root/.local/bin"
 ENV NODE_ENV production
 WORKDIR /app

wasp-ai/src/server/jobs/failStaleGenerations.ts

@@ -8,12 +8,11 @@ export const failStaleGenerations: FailStaleAppsJobs<
     success: boolean;
   }
 > = async (_args, context) => {
-  // If a generation has been in progress for > 5 minutes, it fails it
   log("Failing stale generations");
   const { Project, Log } = context.entities;
 
   const now = getNowInUTC();
-  const fiveMinutesAgo = new Date(now.getTime() - 5 * 60 * 1000);
+  const fiveMinutesAgo = new Date(now.getTime() - 10 * 60 * 1000);
 
   try {
     const staleProjects = await Project.findMany({

waspc/src/Wasp/AI/OpenAI/ChatGPT.hs

@@ -44,7 +44,7 @@ queryChatGPT apiKey params requestMessages = do
       request =
         -- 90 seconds should be more than enough for ChatGPT to generate an answer, or reach its own timeout.
         -- If it proves in the future that it might need more time, we can increase this number.
-        HTTP.setRequestResponseTimeout (HTTP.C.responseTimeoutMicro $ Util.secondsToMicroSeconds 90) $
+        HTTP.setRequestResponseTimeout (HTTP.C.responseTimeoutMicro $ Util.secondsToMicroSeconds 300) $
           HTTP.setRequestHeader "Authorization" [BSU.fromString $ "Bearer " <> apiKey] $
             HTTP.setRequestBodyJSON reqBodyJson $
               HTTP.parseRequest_ "POST https://api.openai.com/v1/chat/completions"