Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Facing error while using @salesforce/core on AWS serverless #2553

Closed
thebedroomprogrammer opened this issue Nov 3, 2023 · 4 comments
Closed
Labels
bug Issue or pull request that identifies or fixes a bug more information required Issue requires more information or a response from the customer

Comments

@thebedroomprogrammer
Copy link

Summary

I am using the @salesforce/core package and just upgraded to version 5.2.9. The issue that I am running into now is that when running the code on the server I get the error ERROR Error: unable to determine transport target for "../../lib/logger/transformStream", even though I am using the flag SF_DISABLE_LOG_FILE: true in my env file to disable the logs. This was not happening in the previous version as the logger was honouring the flag passed in the env file.

I looked at the code and I think that this is the code that is causing the issue.

Steps To Reproduce

Any serverless project that uses the @salesforce/core package with the version. 5.2.9 with AWS serverless should have the issue with the logs disabled.

Expected result

Since I had not opted for the logs I should not have got the error.

Actual result

Serverless function threw an error
ERROR Error: unable to determine transport target for "../../lib/logger/transformStream"

System Information

I am using zsh

Screenshot 2023-11-03 at 11 28 11 AM
@thebedroomprogrammer thebedroomprogrammer added the investigating We're actively investigating this issue label Nov 3, 2023
Copy link

github-actions bot commented Nov 3, 2023

Hello @thebedroomprogrammer 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).

A few more things to check:

  • Make sure you've provided detailed steps to reproduce your issue.
    • A repository that clearly demonstrates the bug is ideal.
  • Make sure you've installed the latest version of Salesforce CLI. (docs)
    • Better yet, try the rc or nightly versions. (docs)
  • Try running the doctor command to diagnose common issues.
  • Search GitHub for existing related issues.

Thank you!

@github-actions github-actions bot added more information required Issue requires more information or a response from the customer and removed investigating We're actively investigating this issue labels Nov 3, 2023
Copy link

github-actions bot commented Nov 3, 2023

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

@shetzel
Copy link
Contributor

shetzel commented Nov 3, 2023

@thebedroomprogrammer - the stack trace doesn't show it but I'm assuming the Logger creation is happening from other classes in @salesforce/core right? It should be an easy fix to get in. Thanks for reporting.

@shetzel shetzel added bug Issue or pull request that identifies or fixes a bug and removed more information required Issue requires more information or a response from the customer labels Nov 3, 2023
Copy link

git2gus bot commented Nov 3, 2023

This issue has been linked to a new work item: W-14424066

@github-actions github-actions bot added the more information required Issue requires more information or a response from the customer label Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug more information required Issue requires more information or a response from the customer
Projects
None yet
Development

No branches or pull requests

3 participants