Question:
It feels like the memory should always allow one file (Assuming it’s not over ~10MB or so), however a single 20621byte file (~21KB) exceeds the limit for Replit AI.
Thank you for sharing this issue @Firepup650 and the example file that reproduces. I’m going to report this to our internal team and I’ll let you know once I receive an update.
Thank you for letting us know @ColinWinhall . We are actively looking into options to resolve the issue. Would you like to provide the file so our developers have another user example?
Thanks for the followup @ColinWinhall . Yes, we are planning to fix this, but I don’t have an ETA for you just yet.
Until then, I know it’s not ideal and I agree the file is already a smaller size, but you can try to shorten the file or or use snippets/lines that convey or explain the issue. I’ll keep this thread updated as I hear back from the team.
Seconding this issue. Running out of memory with <300 lines of code.
Wonder if maybe it has to do with importing a lot of modules? In case it’s helpful, below is a list of my modules.
Along with the surprise of learning that Advanced AI is metered, it’s disappointing that there is limited file memory for using AI when paying for a Pro plan.
import os
import datetime
import requests
from fpdf import FPDF
from PyPDF2 import PdfReader
import openai
import re
from bs4 import BeautifulSoup
from google.oauth2.service_account import Credentials
from googleapiclient.discovery import build
from googleapiclient.http import MediaFileUpload
from pydrive.auth import GoogleAuth
from pydrive.drive import GoogleDrive
import urllib.request
import shutil
from pydub import AudioSegment
Hi All. Thank you for waiting. The team has made changes to the input content limits for Replit Core users. You can now receive a longer content length on files and on input for the Advanced AI model.
I tested with some of the files provided and it works great. I can even reference multiple of those files that individually exceeded memory before. The only thing I would note is that you may have to restart your session or clear your browser cache to see the changes.