main.js · part 267

60 text occurrences from desktop/Cursor.app/Contents/Resources/app/extensions/cursor-agent-host/dist/main.js, part 267. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

use strict

use strict

Invalid event target

Invalid event target

use strict

path must be a string

path must be an absolute URL or start with a slash

invalid request path

method must be a string

invalid request method

upgrade must be a string

invalid headersTimeout

invalid bodyTimeout

invalid reset

invalid expectContinue

body must be a string, a Buffer, a Readable stream, an iterable, or an async iterable

headers array must be even

headers must be an object or an array

Form-Data bodies are only supported in node v16.8 and newer.

"content-type: ${t}\r\n"

"content-type: ${o.type}\r\n"

headers array must be even

headers must be an object or an array

invalid ${e} header

invalid ${e} header

"${e}: ${t}\r\n"

invalid ${t} header

invalid ${t} header

invalid content-length header

invalid transfer-encoding header

invalid connection header

invalid keep-alive header

invalid upgrade header

expect header not supported

invalid header key

use strict

use strict

use strict

use strict

use strict

(unknown path)

(unknown path)

(unknown path)

(unknown path)

${0===n||r>=100?Math.round(r).toString():r.toFixed(1)} ${t[n]}

- Agent-store quota exceeded: ${"eager"===t?`your write to "${r}" was rejected`:`a write to "${r}" was rejected`} because the ${function(e){switch(e){case"user":return"user";case"team":return"team";case"service_account":return"service account";default:return"store"}}(e.scope_kind)} storage quota is full (using ~${c(e.usage_bytes)} of ${c(e.limit_bytes)}). Nothing was written; your local copy is intact. To recover: delete files you no longer need — including resolved *.conflict* files, which count toward usage — or truncate large files, or ask a team admin to raise the quota. Deletion frees space within about a minute. Do not retry the same write without freeing space first.

your write to "${r}" was rejected

a write to "${r}" was rejected

service account

- a local write to "${t}" lost a sync race, detected after this call; your losing bytes were preserved remotely and will appear at "${r}" after the next pull. Reconcile the two versions, then truncate the conflict file to empty to resolve.

- a local write to "${t}" lost a sync race, detected after this call; your losing bytes were preserved at "${r}" and the remote winner is now at "${t}". Reconcile the two versions, then delete the conflict file (or truncate it to empty) to resolve.

- a local write to "${t}" lost a sync race, detected after this call; the conflict copy could not be saved, so only the remote winner survives at "${t}". Re-apply your change if needed.

- a local truncate of "${t}" could not be completed after a sync race; inspect the file before relying on it.

- your write to "${t}" lost a sync race: a newer remote version won, so your bytes did NOT persist there. Your losing bytes were preserved remotely and will appear at "${r}" after the next pull. Reconcile the two versions, then truncate the conflict file to empty to resolve.

- your write to "${t}" lost a sync race: a newer remote version won, so your bytes did NOT persist there. Your losing bytes were preserved at "${r}" and the remote winner is now at "${t}". Reconcile the two versions, then delete the conflict file (or truncate it to empty) to resolve.

- your write to "${t}" lost a sync race: a newer remote version won and the conflict copy could not be saved, so only the remote winner survives at "${t}". Re-apply your change if needed.

- your truncate of "${t}" could not be completed after a sync race; inspect the file before relying on it.

Agent-store sync conflict on the file you just wrote:

Agent-store sync conflicts on the files you just wrote (${a.length}):

- (+${u} more conflict${1===u?"":"s"})