Stream oversized generic attachments to disk instead of silently dropping chunks, avoid loading completed file downloads into renderer memory, and surface a clear error when the browser client cannot receive a file. Co-authored-by: Cursor <cursoragent@cursor.com>
16 lines
872 B
JSON
16 lines
872 B
JSON
{
|
|
"attachment": {
|
|
"errors": {
|
|
"noConnectedPeers": "No connected peers are available to provide this file right now.",
|
|
"fileNotFound": "The connected peers do not have this file right now.",
|
|
"uploaderLocalMissing": "Your original upload could not be found on this device. Re-upload the file to restore playback.",
|
|
"prepareDownloadFailed": "Could not prepare media download on disk.",
|
|
"chunksOutOfOrder": "Received media chunks out of order. Retry the download.",
|
|
"writeDownloadFailed": "Could not write media download to disk.",
|
|
"openDownloadFailed": "Could not open completed media download from disk.",
|
|
"downloadFailed": "Media download failed. Retry the download.",
|
|
"fileTooLarge": "This file is too large to download in this client. Use the desktop app or ask the sender to share a smaller file."
|
|
}
|
|
}
|
|
}
|