Strange infinite loop artifact #31
Description
After a couple of sst dev runs, I run into this thing. It goes away by removing the .sst folder.
The path doesn't actually exist in the system, it just thinks it does.
Error: ENAMETOOLONG: name too long, scandir '/Users/culda/xx-main/apps/ops/chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@xx-labs/ops-chat/.sst/artifacts/OCServer-dev/node_modules/@aws-solutions-constructs/aws-cloudfront-s3/test/integ.cfts3-bucket-encrypted-with-cmk-provided-as-existingbucket.js.snapshot/asset.4dc48ffba382f93077a1e6824599bbd4ceb6f91eb3d9442eca3b85bdb1a20b1e'
sst.config.ts
const server = new sst.aws.OpenControl('OC', {
server: {
handler: 'src/server.handler',
link: [anthropicKey, envs],
permissions: [
{
actions: ['sts:AssumeRole'],
resources: [ssmRole],
},
{
actions: ['states:RedriveExecution', 'states:DescribeExecution'],
resources: ['*'],
},
],
},
});
Metadata
Metadata
Assignees
Labels
No labels