[Bug]: Unable to run project on macOS 13
See original GitHub issueIs there an existing issue for this?
- I have searched the existing issues
Issue Details
I am following the contributing guide
It’s working on Linux without any issues. but on mac, there is an issue with applying the patches.
when I run quilt push -a
there are errors.
Am I missing something?
Steps to Reproduce
- Follow the contribution guide on Mac M1
Expected
The patches should be applied
Actual
There are errors and I get a forbidden message when I run code-server on the browser. According to the docs, this happens when the patches are not applied correctly
Logs
Applying patch patches/proposed-api.diff
patching file 'lib/vscode/src/vs/workbench/services/extensions/common/abstractExtensionService.ts'
Can't backup '/var/folders/f1/bwc053990rg36bl7bc6bv6940000gn/T/patchoQQ2sGvMSLk', output is in '/var/folders/f1/bwc053990rg36bl7bc6bv6940000gn/T/patchoQQ2sGvMSLk': No such file or directory
patching file 'lib/vscode/src/vs/workbench/services/extensions/common/extensions.ts'
Can't backup '/var/folders/f1/bwc053990rg36bl7bc6bv6940000gn/T/patchoQQ2sGvMSLk', output is in '/var/folders/f1/bwc053990rg36bl7bc6bv6940000gn/T/patchoQQ2sGvMSLk': No such file or directory
Patch patches/proposed-api.diff appears to be empty; applied
Applying patch patches/marketplace.diff
patching file 'lib/vscode/src/vs/platform/product/common/product.ts'
Can't backup '/var/folders/f1/bwc053990rg36bl7bc6bv6940000gn/T/patchoIe3etLqZrR', output is in '/var/folders/f1/bwc053990rg36bl7bc6bv6940000gn/T/patchoIe3etLqZrR': No such file or directory
patching file 'lib/vscode/src/vs/server/node/webClientServer.ts'
Can't backup '/var/folders/f1/bwc053990rg36bl7bc6bv6940000gn/T/patchoIe3etLqZrR', output is in '/var/folders/f1/bwc053990rg36bl7bc6bv6940000gn/T/patchoIe3etLqZrR': No such file or directory
patching file 'lib/vscode/src/vs/platform/extensionResourceLoader/common/extensionResourceLoader.ts'
Can't backup '/var/folders/f1/bwc053990rg36bl7bc6bv6940000gn/T/patchoIe3etLqZrR', output is in '/var/folders/f1/bwc053990rg36bl7bc6bv6940000gn/T/patchoIe3etLqZrR': No such file or directory
1 out of 2 hunks failed--saving rejects to 'lib/vscode/src/vs/platform/extensionResourceLoader/common/extensionResourceLoader.ts.rej'
Patch patches/marketplace.diff does not apply (enforce with -f)
Issue Analytics
- State:
- Created 10 months ago
- Comments:18 (8 by maintainers)
Top Results From Across the Web
Xcode 13 cannot run project genera… - Apple Developer
Open Xcode 12.5.1 and generate a new empty ios app. · Press Run and see how it builds and runs on your device....
Read more >macOS Ventura bug disables security software - Malwarebytes
Apple's initial release of macOS 13, named "Ventura," contains a nasty bug that causes important functionality of all third-party security ...
Read more >How to fix common macOS Ventura issues - Setapp
We explore the top 10 Ventura problems and best ways to fix them, from installation issues to Mac running slow on Ventura.
Read more >macOS Ventura problems and how to fix them - MacPaw
How to fix an unstable macOS Ventura on Mac? In case macOS Ventura behaves erratically, first, update your apps. Then use Activity Monitor...
Read more >Apple Releases macOS Ventura 13.0.1 Update With Bug Fixes
The new software comes two weeks after the official launch of Ventura. Ventura Macs Feature Yellow The macOS Ventura update can be ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI, you can work around this problem by installing GNU patch on a Mac using homebrew:
Be sure to close your existing console window and open a new one after installing it to test this (otherwise it may still use the original Apple “patch”).
Another workaround would be to run the command inside a docker container.