754.js · part 1

24 text occurrences from desktop/Cursor.app/Contents/Resources/app/extensions/cursor-local-agent-runtime/dist/754.js, part 1. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

use strict

Unable to connect to instance metadata service

TimeoutError from instance metadata service

Error response received from instance metadata service

Invalid response received from instance metadata service.

${t.hostname} is not a valid container metadata service hostname

${t.protocol} is not a valid container metadata service protocol

The container metadata credential provider cannot be used unless the ${g} or ${f} environment variable is set

Unsupported endpoint mode: ${e}. Select from ${Object.values(N)}

Attempting credential expiration extension due to a credential service availability issue. A refresh of these credentials will be attempted after ${new Date(n)}.
For more information, please visit: https://docs.aws.amazon.com/sdkref/latest/guide/feature-static-credentials.html

Credential renew failed: 

${O} not set in env, checking config file next.

credential provider initialization (runtime option ec2MetadataV1Disabled)

config file profile (${M})

process environment variable (${O})

AWS EC2 Metadata v1 fallback has been blocked by AWS SDK configuration in the following: [${n.join(", ")}].

AWS SDK Instance Metadata

using v1 fallback (no token fetch)

EC2 Metadata token request returned error

AWS SDK Instance Metadata

using v1 fallback (initial)

Invalid response received from instance metadata service.

Not found in ENV: ${i(g.toString())}

Not found in config files w/ profile [${n}]: ${i(e.toString())}