logger.error prints the stacktrace of line where it was invoked

[orestesgaolin]

Related issues

Somewhat related to:

• Warn log messages are being displayed as errors #1580
• Missing traces in firebase functions using express, again #1625

[REQUIRED] Version info

node: 20

firebase-functions: 6.2.0

firebase-tools: 13.30.0

firebase-admin: 12.6.0

[REQUIRED] Test case

import { logger } from "firebase-functions/v2";
import { onCall } from "firebase-functions/v2/https";

export const functionName = onCall({region: ["europe-west1"]}, async (req) => {
  logger.error("User is not allowed to upload data for this userId", [ "234", "123" ]);
})

[REQUIRED] Steps to reproduce

[REQUIRED] Expected behavior

Error stacktrace should not be printed in plain text if not provided

[REQUIRED] Actual behavior

Code sample above results with following outcome in GCP Logging:

Were you able to successfully deploy your functions?

Yes

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[CorieW]

Hi @orestesgaolin,

Thanks for reporting this issue! We’ve received it and are reviewing it. We’ll provide updates as soon as possible.

[CorieW]

I'll bring this up with the team.