Had anyone ever seen an error like this with #AWSLambda?

It's a Node 18 app that calls out to Renovate but fails due to some deep intenals in Node when doing some performance checking?

{
    "errorType": "TypeError",
    "errorMessage": "performance.markResourceTiming is not a function",
    "stack": [
        "TypeError: performance.markResourceTiming is not a function",
        "    at markResourceTiming (node:internal/deps/undici/undici:10636:21)",
        "    at finalizeAndReportTiming (node:internal/deps/undici/undici:10632:7)",
        "    at Object.handleFetchDone [as processResponseEndOfBody] (node:internal/deps/undici/undici:10579:45)",
        "    at node:internal/deps/undici/undici:10895:44",
        "    at node:internal/process/task_queues:140:7",
        "    at AsyncResource.runInAsyncScope (node:async_hooks:204:9)",
        "    at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)",
        "    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"
    ]
}

Very odd, and this Go issue is the only thing I could find that may relate 🤔

by Jamie Tanna's profile image Jamie Tanna . #aws-lambda.

Also on:

This post was filed under notes.

Interactions with this post

Interactions with this post

Below you can find the interactions that this page has had using WebMention.

Have you written a response to this post? Let me know the URL:

Do you not have a website set up with WebMention capabilities? You can use Comment Parade.