The latest updates on your projects. Learn more about Vercel for Git ↗︎

The preview deployment failed. 🔴

Open Build Logs

Last updated at: 2024-11-12 20:37:28 CET

Hey @minump, here is an example of how you can ask me to improve this pull request:

@Sweep Add unit tests for the `buildPrompt` API endpoint that verify the new 4mb size limit configuration works as expected, testing both valid requests under the limit and requests that exceed it.

📖 For more information on how to use Sweep, please read our documentation.

Had a bug that gives a 413 error (payload too large) for POST buildPrompt api.

Tried configuring the request body size limit to be higher in src/pages/api/buildPrompt.ts and src/pages/api/chat-api/chat.ts

export const config = {
  api: {
      bodyParser: {
          sizeLimit: '4mb'  # less than 4.5 mb size limit from vercel
      }
  }
}

This and reducing the top_n in the retriever helped to continue the conversation for 4-5 chats, but it fails nevertheless because of the whole conversation is being passed around in these api calls.

This is fixed with the current PR merge with changing the buildPrompt and routeModelRequest to be server function code rather than api calls.

As a next step, the conversations should also be fetched from the db. All previous conversations should be fetched from the db. Only the conversation id and the current user input needs to be input parameters in the api calls.