Source conversion failing with multiple large .zip static resources about cli HOT 9 CLOSED

Good news so far, updating to 7.200.7 seems to have fixed the issue for me when running locally on my machine!

I'd imagine this update will fix the same issue when running in our devops pipeline as well. I'll post an update here later today after some testing and close the issue if all is well.

from cli.

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.

from cli.

can you open that repo up publicly so I can try with your code?

from cli.

@mshanemc I've added you as a contributor to that repo.

I will add other users as needed, but have been asked to keep the repo private as it contains source code from a production environment.

Thanks!

from cli.

Thanks for the access! I totally believe you because there's some people who can repro a packaging bug involving multiple static resources. There's a bug somewhere in 7.199

Unfortunately, neither Steve nor I can get the bug to appear.

sfv2

I even uninstalled and downgraded to the version you're on and it seems to work fine.

sfdx latest

from cli.

not memory related. this works fine:
NODE_OPTIONS='--max-old-space-size=2000' sf force source convert -x manifest/package.xml --output-dir mdapiOut

from cli.

Yikes! As a sanity check I just updated to 7.200.6, freshly cloned the repo, and tested again. Still getting the same results:

Individual file succeeds:

Both files at once, doesn't succeed:

Both files at once, using old version succeeds:

Looks like we're both on the trusty Salesforce MacBook, so there should be minimal difference in OS, etc. Other than something very silly like memory or file structure differences, I couldn't imagine what would make the difference

Let me know if there's anything else I could provide to help repro. I think my team can just use the older version for now as a workaround.

Thanks for looking into this!

from cli.

We've got some workarounds and a fixed RC available. I'd love to know that this is working for you.
#2125

from cli.

We've had success running 7.200.7 in our devops pipelines today, so it seems the fix worked for us.

If only those amateurs working on Node.js could get their act together, am I right??

from cli.