Leo Hanisch
Leo Hanisch
In the meantime we explicitly override the dependency in the `package.json` like this: ```jsonc { "dependencies": { // your dependencies ... }, "overrides": { "@automapper/classes": { "reflect-metadata": "^0.2.2" }, "@automapper/nestjs":...
Hi @CrypticCabub thx for your response. I meant it slightly different. We use a single instance for both teams. Therefore, we want either one instance Support multiple schedules or better...
@frogamic thx for stepping in. That's essentially what I've meant 😅. Thx for reopening @CrypticCabub 🙏🏼.
@eahefnawy To reduce the lambda function's bundle size we'd prefer to use the file extension `.mjs` instead of adding an additional file to the bundle.
@eahefnawy in case you meant why not setting that in the project's workspace directory that would not work for us either because we have a monorepo setup and not all...
@eahefnawy Yes, we don't want to add a package.json file to the lambda bundle.
Hi @dreamorosi, thx for the swift reply. I wasn't aware that this is limited to the usage of the agent. I guess the major concern about using the agent directly...
Is there maybe a workaround to disable the logging of that error? This error message clutters our logs 😅.
Thx for the answer, I'll try that.
I can confirm that with the environment variable `AWS_XRAY_CONTEXT_MISSING` set to `IGNORE_ERROR` the error is no longer logged 👍🏼. Thank you for the hint @dreamorosi.