App on community cloud outputs some DEBUG logs not need frequently

my app URL is https://creativechatbot-abogjzaxobsqmnsmovwrv5.streamlit.app/,

python version is 3.11

built from my private GitHub repo, requirements are:
dashscope==1.13.5
faiss-cpu==1.7.4
langchain==0.0.340
pandas==2.0.3
pydantic==1.10.12
rich==13.5.2
streamlit==1.29.0
streamlit_chat

frequently output logs like
DEBUG [03:53:49] - DEBUG - in-event <InotifyEvent: inotify_buffer.py:59
src_path=b’/mount/src/creativechatbot/src/messages’, wd=7, mask=IN_ISDIR|IN_OPEN,
cookie=0, name=‘’>
DEBUG [03:53:49] - DEBUG - in-event <InotifyEvent: inotify_buffer.py:59
src_path=b’/mount/src/creativechatbot/src/prompt’, wd=1, mask=IN_ISDIR|IN_OPEN,
cookie=0, name=‘prompt’>
DEBUG [03:53:49] - DEBUG - in-event <InotifyEvent: inotify_buffer.py:59
src_path=b’/mount/src/creativechatbot/src/prompt’, wd=4, mask=IN_ISDIR|IN_OPEN,
cookie=0, name=‘’>
DEBUG [03:53:49] - DEBUG - in-event <InotifyEvent: inotify_buffer.py:59
src_path=b’/mount/src/creativechatbot/src/prompt/pycache’, wd=4,
mask=IN_ISDIR|IN_OPEN, cookie=0, name=‘pycache’>
DEBUG [03:53:49] - DEBUG - in-event <InotifyEvent: inotify_buffer.py:59
src_path=b’/mount/src/creativechatbot/src/prompt/pycache’, wd=13,
mask=IN_ISDIR|IN_OPEN, cookie=0, name=‘’>
DEBUG [03:53:49] - DEBUG - in-event <InotifyEvent: inotify_buffer.py:59
src_path=b’/mount/src/creativechatbot/src/utils’, wd=1, mask=IN_ISDIR|IN_OPEN,
cookie=0, name=‘utils’>
DEBUG [03:53:49] - DEBUG - in-event <InotifyEvent: inotify_buffer.py:59
src_path=b’/mount/src/creativechatbot/src/utils’, wd=3, mask=IN_ISDIR|IN_OPEN,
cookie=0, name=‘’>
DEBUG [03:53:49] - DEBUG - in-event <InotifyEvent: inotify_buffer.py:59
src_path=b’/mount/src/creativechatbot/src/utils/pycache’, wd=3,
mask=IN_ISDIR|IN_OPEN, cookie=0, name=‘pycache’>
DEBUG [03:53:49] - DEBUG - in-event <InotifyEvent: inotify_buffer.py:59
src_path=b’/mount/src/creativechatbot/src/utils/pycache’, wd=14,
mask=IN_ISDIR|IN_OPEN, cookie=0, name=‘’>

Hey @Qin_Reking,

Thanks for sharing this question. Would you be able to share a public version of your GitHub repo that will allow us to reproduce this behavior? Unfortunately it is quite difficult for us to diagnose the root cause without looking at your code.