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

REGRESSION: SFDX 7.176 silently exits when pushing Zipfile static resource #1791

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

Comments

@daveespo
Copy link

daveespo commented Nov 4, 2022

Summary

Our nightly CI build for the CLI Release Candidate failed tonight on CLI sfdx-cli/7.176.0

Through binary debugging of removing one metadata type at a time, I was able to isolate it down to the expanded static resources in our source tree. I created a repo below with an example static resource that exhibits the problem. I was unable to generate log files for some reason -- sfdx.log never got created?

Steps To Reproduce:

Repository to reproduce:

https://github.com/patronmanager/regression-176-staticresource

  1. Clone the above repo
  2. sfdx force:org:create --setdefaultusername -f config/project-scratch-def.json
  3. sfdx force:source:push

Expected result

Expected the static resource to be pushed into the org

Actual result

Command immediately exits with no error

esposito@PT-WIN-ESPOSITO:~/regression-176-staticresource$ sfdx force:source:push
*** Pushing with SOAP API v55.0 ***
esposito@PT-WIN-ESPOSITO:~/regression-176-staticresource$ 

Note that I tried generating log output but even using --loglevel debug didn't generate an sfdx.log for me

System Information

Same failure on both the current GH Actions default ubuntu-latest container as well as WSL

 CLI Version:
        sfdx-cli/7.176.0

 Architecture:
        wsl-x64

 Node Version:
        node-v18.12.0

 Plugin Version:
        @oclif/plugin-autocomplete 1.3.5 (core)
        @oclif/plugin-commands 2.2.1 (core)
        @oclif/plugin-help 5.1.17 (core)
        @oclif/plugin-not-found 2.3.3 (core)
        @oclif/plugin-plugins 2.1.1 (core)
        @oclif/plugin-update 3.0.6 (core)
        @oclif/plugin-version 1.1.3 (core)
        @oclif/plugin-warn-if-update-available 2.0.6 (core)
        @oclif/plugin-which 2.1.1 (core)
        alias 2.1.7 (core)
        apex 1.3.0 (core)
        auth 2.2.19 (core)
        community 2.0.14 (core)
        config 1.4.22 (core)
        custom-metadata 2.0.3 (core)
        data 2.1.7 (core)
        generator 2.0.9 (core)
        info 2.2.4 (core)
        limits 2.0.10 (core)
        org 2.2.11 (core)
        packaging 1.9.8 (core)
        schema 2.1.12 (core)
        signups 1.2.11 (core)
        source 2.3.0 (core)
        telemetry 2.0.2 (core)
        templates 55.1.0 (core)
        trust 2.0.4 (core)
        user 2.1.16 (core)
        @salesforce/sfdx-plugin-lwc-test 1.0.1 (core)
        salesforce-alm 54.8.3 (core)

 OS and Version:
        Linux 5.10.102.1-microsoft-standard-WSL2

 Shell:
        bash

 Root Path:
        /home/esposito/sfdx

Additional information

Feel free to attach a screenshot.

@daveespo daveespo added the investigating We're actively investigating this issue label Nov 4, 2022
@github-actions
Copy link

github-actions bot commented Nov 4, 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.

@mshanemc
Copy link
Contributor

mshanemc commented Nov 4, 2022

I'm going to fix this and patch RC with it.

@mshanemc mshanemc 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-12009115

@daveespo
Copy link
Author

daveespo commented Nov 4, 2022

@mshanemc -- thanks for the quick turnaround! I re-ran the build that was failing and it passes on 7.176.1.

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

2 participants