Website handle server errors more gracefully · LAION-AI/Open-Assistant#3533

2023-06-29T00:52:41.000Z

Back end: - on or around 2023.6.25— Since we surpassed ~3000 concurrent requests 30B_7 has been down from user load. 30B_6 seemed to be working with page refresh. Front end: - 2023.6.27— the front end stopped showing new replies without page refresh. - 2023.6.28— showing me logged in on front page, but logged out in Chat section. - 2023.6.28— site frequently gone altogether & replaced with error message `Internal Server Error`

(2 comments) (0 reactions) (0 assignees)Python (37,363 stars) (3,263 forks)batch import

buggood first issuewebsite

説明

Back end:

on or around 2023.6.25— Since we surpassed ~3000 concurrent requests 30B_7 has been down from user load. 30B_6 seemed to be working with page refresh.

Front end:

2023.6.27— the front end stopped showing new replies without page refresh.
2023.6.28— showing me logged in on front page, but logged out in Chat section.
2023.6.28— site frequently gone altogether & replaced with error message Internal Server Error

コントリビューターガイド

技術スタック: pythonjavascript
領域: full stack
Issue 種別: bug
難度: 3
推定時間: half day
活動状況: stale
明確さ: needs investigation
前提条件: Basic knowledge of Python backendUnderstanding of HTTP error handling
初心者向け度: 35
調査方針: Investigate the Open Assistant backend (likely Python) and frontend code to identify how server errors are currently displayed. Look for error handling middleware and frontend error boundaries. Consider implementing a user friendly error page and retry mechanism. Check comments on the issue for any additional context.