[Bug]: Shopify theme init is not working
Please confirm that you have:
- [X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
- [X] Reproduced the issue in the latest CLI version.
In which of these areas are you experiencing a problem?
Theme
Expected behavior
By running command shopify theme init i get this error every time , i have re installed node, ruby dev kit , git, and shopify cli to ensure my system is working properly but getting this error again and again. Here it is for your reference--
Actual behavior
Receiving objects: 33% (7722/23398), 14.20 │B | 222.00 KiB/s error: RPC failed; curl 18 │98), 14.37 MiB | 233.00 KiB/s │ transfer closed with outstanding read data remaining │ │ error: 7436 bytes of body are still expected │ │ fetch-pack: unexpected disconnect while reading sideband packet │ │ fatal: early EOF │ │ fatal: fetch-pack: invalid index-pack output
Verbose output
2024-04-10T04:10:13.552Z: Unable to log analytics event - no information on executed command 2024-04-10T04:10:13.558Z: Reporting handled error to Bugsnag: Cloning into 'G:/Next projects/Shopify Theme/OxiBT'... remote: Enumerating objects: 23360, done. remote: Counting objects: 100% (105/105), done. remote: Compressing objects: 100% (62/62), done. error: RPC failed; curl 18 transfer closed with outstanding read data remaining error: 2554 bytes of body are still expected fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output
Reproduction steps
1.Checked my node 2.Checked my ruby version 3.Checked shopify cli version to ensure everything installed properly
Operating System
Windows 11
Shopify CLI version (check your project's package.json if you're not sure)
Current Shopify CLI version: 3.58.2
Shell
Git bash
Node version (run node -v if you're not sure)
Node.js v20.11.1
What language and version are you using in your application?
ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [x64-mingw-ucrt]
is there anyone who could help??
If you don't mind kindly let have few discussions on the theme issue so kindly follow me back so we can discuss
sure tell me??
This issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action. → If there's no activity within a week, then a bot will automatically close this. Thanks for helping to improve Shopify's dev tooling and experience.
P.S. You can learn more about why we stale issues here.
Thanks for your prompt response
On Tue, 28 May 2024, 04:35 github-actions[bot], @.***> wrote:
This issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action. → If there's no activity within a week, then a bot will automatically close this. Thanks for helping to improve Shopify's dev tooling and experience.
P.S. You can learn more about why we stale issues here https://github.com/Shopify/cli/blob/main/docs/decision-record/2023_02-Stale-action.md .
— Reply to this email directly, view it on GitHub https://github.com/Shopify/cli/issues/3674#issuecomment-2134289266, or unsubscribe https://github.com/notifications/unsubscribe-auth/A44WXXIG7VZAXFYEWKZK7FLZEP3O7AVCNFSM6AAAAABF56Q2UCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUGI4DSMRWGY . You are receiving this because you commented.Message ID: @.***>
Hi @min23a,
Thanks for reporting this issue!
Shopify CLI calls Git under the hood to execute git clone https://github.com/shopify/dawn and use Dawn as a starting point.
Based on the logs, it seems like that call to Git is failing. Could you please confirm the following details:
- Do you face the same error when running
git clone https://github.com/shopify/dawndirectly? - Are you using Git 2.28.0 or higher?
On Windows, the CLI has the limitation of working strictly with Ruby 3.0, so ensuring you're using that Ruby version might help resolve the issue.
Additionally, if those pointers don't help, the full --verbose output would be really valuable for the team to understand the scenario that you're facing.
Thanks again for reporting this issue!
👋🏻 Hey @min23a, because there hasn’t been activity in the last couple of weeks we’ll be closing this issue. However if you’re still experiencing the same problem, please reopen the issue and share the outstanding context we’ve requested. Thanks!