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

setting up repository locally always create issues on Windows. #30341

Open
naaajii opened this issue Jan 16, 2025 · 1 comment
Open

setting up repository locally always create issues on Windows. #30341

naaajii opened this issue Jan 16, 2025 · 1 comment
Labels
docs This issue is related to documentation needs triage This issue needs to be triaged by the team

Comments

@naaajii
Copy link
Contributor

naaajii commented Jan 16, 2025

Documentation Feedback

I don't have my own system so I use my work laptop to contribute and I'm always juggling between different laptops so I have to setup again and again. Setting up repository on Ubuntu seems fairly easy & works out of the box but Windows bothers alot. I have been using a Windows 11 for past few months & whenever I find free time to contribute I struggle to run on Windows 10 & 11 all the time.

I have been provided a new laptop & I'm facing issues such as:

  1. error Couldn't find match for in "refs/heads/main" for "https://github.com/angular/dev-infra-private-ng-dev-builds.git".
    info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Sometimes gets fixed on yarn cache clear, mostly happens whenever I update the work and run yarn after a long time.

  1. iBazel [1:54PM]: Error writing failure to stdin: write |1: file already closed

happens all the time, gets fixed sometimes when I delete bazel folders and end all processes from task manager.

  1. iBazel [1:08PM]: Error starting process: fork/exec C:\Users\CENTRI1\AppData\Local\Temp\bazel_script_path4055922069.bat: %1 is not a valid Win32 application.
    iBazel [1:08PM]: Run start failed fork/exec C:\Users\CENTRI
    1\AppData\Local\Temp\bazel_script_path4055922069.bat: %1 is not a valid Win32 application.

I checked the bat file and its 0kb so I'm not sure whats causing it to generate an empty file. I also have added BAZEL_SH to the environment variables. I also came across other issues where peopled claimed its caused by WSL on Windows but I have had it disabled it on both work laptops. I also have used bash and Windows command to run the project but errors are always the same.

Affected documentation page

https://github.com/angular/components/blob/1e5663636eb38d5556f500840dd7e00dd9950b70/DEV_ENVIRONMENT.md?plain=1

@naaajii naaajii added docs This issue is related to documentation needs triage This issue needs to be triaged by the team labels Jan 16, 2025
@naaajii
Copy link
Contributor Author

naaajii commented Jan 16, 2025

I also got this new error recently:

ERROR: D:/open-source/components/src/cdk/a11y/BUILD.bazel:13:10: Compiling Angular templates (full devmode) //src/cdk/a11y:a11y failed: (Exit 1): ngc-wrapped.bat failed: error executing command bazel-out\x64_windows-opt-exec-2B5CBBC6\bin\external\npm\@angular\bazel\bin\ngc-wrapped.bat --node_options=--expose-gc --node_options=--stack-trace-limit=100 --node_options=--max-old-space-size=4096 ... (remaining 1 argument skipped)
src/cdk/a11y/key-manager/noop-tree-key-manager.ts:105:14 - error TS2742: The inferred type of 'NOOP_TREE_KEY_MANAGER_FACTORY_PROVIDER' cannot be named without a reference to '../../../../external/npm/node_modules/@angular/core'. This is likely not portable. A type annotation is necessary.

105 export const NOOP_TREE_KEY_MANAGER_FACTORY_PROVIDER = {
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This issue is related to documentation needs triage This issue needs to be triaged by the team
Projects
None yet
Development

No branches or pull requests

1 participant