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

Unexpected Error on Package creation with "force:package:beta:version:create" command #1789

Closed
rsavaliyagit opened this issue Nov 3, 2022 · 13 comments
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue

Comments

@rsavaliyagit
Copy link

Summary

I'm getting below error on package creation with "force:package:beta:version:create" command.

Command: sfdx force:package:beta:version:create --codecoverage -p "PACKAGE" -k "INSTALLATIONKEY" -v "TARGETDEVHUBUSERNAME" --wait 120

(Use node --trace-warnings ... to show where the warning was created)
ERROR running force:package:beta:version:create: Converting circular structure to JSON
--> starting at object with constructor 'Connection'
| property '_refreshDelegate' -> object with constructor 'SessionRefreshDelegate'
--- property '_conn' closes the circle

Steps To Reproduce: Run this command to create a package.

Command: sfdx force:package:beta:version:create --codecoverage -p "PACKAGE" -k "INSTALLATIONKEY" -v "TARGETDEVHUBUSERNAME" --wait 120

Expected result

Package should be created successfully.

Actual result

Error:

ERROR running force:package:beta:version:create: Converting circular structure to JSON
--> starting at object with constructor 'Connection'
| property '_refreshDelegate' -> object with constructor 'SessionRefreshDelegate'
--- property '_conn' closes the circle

System Information

  • Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.) : sfdx-cli/7.174.0
  • If you are using sfdx
    • Run 'sfdx force:package:beta:version:create --codecoverage -p "PACKAGE" -k "INSTALLATIONKEY" -v "TARGETDEVHUBUSERNAME" --wait 120'
  • Paste the output here
@rsavaliyagit rsavaliyagit added the investigating We're actively investigating this issue label Nov 3, 2022
@github-actions
Copy link

github-actions bot commented Nov 3, 2022

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.

@peternhale
Copy link
Contributor

@rsavaliyagit I would like some additional information please.

  • results of running sfdx version --verbose
  • If you can, share the contents of sfdx-project.json
  • the files created by `sfdx doctor -c "force📦beta:version:create --codecoverage -p "PACKAGE" -k "INSTALLATIONKEY" -v "TARGETDEVHUBUSERNAME" --wait 120" (please examine the resulting files to redact any sensitive information)

@rsavaliyagit
Copy link
Author

Here are some more details. Please let me know if you need more info. Thanks!

sfdx version --verbose
CLI Version:
sfdx-cli/7.175.0 ( Version on Jenkins Pipeline Server: sfdx-cli/7.174.0)

Architecture:
win32-x64

Node Version:
node-v18.12.0

Plugin Version:
@oclif/plugin-autocomplete 1.3.1 (core)
@oclif/plugin-commands 2.2.0 (core)
@oclif/plugin-help 5.1.14 (core)
@oclif/plugin-not-found 2.3.3 (core)
@oclif/plugin-plugins 2.1.1 (core)
@oclif/plugin-update 3.0.2 (core)
@oclif/plugin-version 1.1.2 (core)
@oclif/plugin-warn-if-update-available 2.0.6 (core)
@oclif/plugin-which 2.1.0 (core)
alias 2.1.6 (core)
apex 1.3.0 (core)
auth 2.2.16 (core)
community 2.0.13 (core)
config 1.4.21 (core)
custom-metadata 2.0.2 (core)
data 2.1.5 (core)
generator 2.0.8 (core)
info 2.2.1 (core)
limits 2.0.8 (core)
org 2.2.9 (core)
packaging 1.9.6 (core)
schema 2.1.11 (core)
signups 1.2.8 (core)
source 2.0.26 (core)
telemetry 2.0.2 (core)
templates 55.1.0 (core)
trust 2.0.4 (core)
user 2.1.14 (core)
@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)
salesforce-alm 54.8.3 (core)

OS and Version:
Windows_NT 10.0.19042

Shell:
cmd.exe


contents of sfdx-project.json

{
"packageDirectories": [
{
"path": "force-app",
"default": true,
"package": "sfdx-sales-lib",
"versionNumber": "22.10.0.NEXT",
"definitionFile": "config/enterprise-scratch-def.json",
"dependencies": [
{
"package": "S3-Link"
},
{
"package": "CMTD Enhanced Related List"
},
{
"package": "Marketing Cloud"
},
{
"package": "sfdx-base-lib",
"versionNumber": "22.10.0.LATEST"
},
{
"package": "Gryphon"
},
{
"package": "ZoomInfo"
},
{
"package": "DOZISF ZoomInfo"
},
{
"package": "UniversalTimeline"
},
{
"package": "PhoneTools"
},
{
"package": "AMSTAT"
}
]
},
{
"path": "manual-metadata",
"default": false
}
],
"namespace": "",
"sfdcLoginUrl": "https://login.salesforce.com",
"sourceApiVersion": "55.0",
"packageAliases": {
packageAliases
}
}

@peternhale
Copy link
Contributor

peternhale commented Nov 4, 2022

@rsavaliyagit Thank you for the information, but could use a bit more,

Are you able to share the results of the sfdx doctor command?

If not, could you return the command agains with the --json flag, so a stack trace can be captured

Does the version create work with the sfdx force:project:create:version command?

@rsavaliyagit
Copy link
Author

Result_sfdx doctor command.txt

attached the result of doctor command.

@peternhale peternhale added the bug Issue or pull request that identifies or fixes a bug label Nov 4, 2022
@git2gus
Copy link

git2gus bot commented Nov 4, 2022

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

@rsavaliyagit
Copy link
Author

Hi @peternhale just checking if you have any update on this issue?

@peternhale
Copy link
Contributor

@rsavaliyagit The issue has been located and corrected. The change was made in packaging library. We hope to have that version include in the plugin commands in this week's latest-rc release of sfdx-cli.

@rsavaliyagit
Copy link
Author

@peternhale thanks for the quick response. what date is the release of sfdx-cli in this week ?

@peternhale
Copy link
Contributor

@rsavaliyagit we typically release each Thursday.

@Charles-Revelle
Copy link

@peternhale can we get confirmation that a fix for this bug is planned for tomorrow (Thursday 11/10)? I work with @rsavaliyagit and we have several deployments dependent on this.

@rsavaliyagit
Copy link
Author

Hi @peternhale Let us know the latest-rc version # once it's available. Thanks!

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 investigating We're actively investigating this issue
Projects
None yet
Development

No branches or pull requests

4 participants