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.

Sign up for GitHub

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

Jump to bottom

Rush Multi-Project Build Tool - Some third-party scripts might produce unexpected results due to the change in macOS version from 10.x to 11. (62477208) #11474

Closed
jay-most opened this issue Sep 24, 2020 · 2 comments
Closed

Rush Multi-Project Build Tool - Some third-party scripts might produce unexpected results due to the change in macOS version from 10.x to 11. (62477208) #11474

jay-most opened this issue Sep 24, 2020 · 2 comments
Assignees
@praveenkuttappan
Labels
Central-EngSys This issue is owned by the Engineering System team. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-author-feedback Workflow: More information is needed from author to address the issue. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@jay-most
Copy link
Contributor

  • Package Name: Rush Multi-Project Build Tool
  • Package Version: 5.28.0
  • Operating system: Mac Big Sur
    Node.js version is 14.10.1 (pre-LTS)
  • Is the bug related to documentation in
    Rush Multi-Project Build Tool 5.28.0
    Describe the bug
    A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:
Rush Multi-Project Build Tool 5.28.0 - https://rushjs.io
Node.js version is 14.10.1 (pre-LTS)
Starting "rush link"
Linking projects together...
ERROR: Internal Error: Cannot load shrinkwrap at
"/azure-sdk-for-js/common/temp/pnpm-lock.yaml"
You have encountered a software defect. Please consider reporting the issue to
the maintainers of this application.

Expected behavior
Known Issues
Some third-party scripts might produce unexpected results due to the change in macOS version from 10.x to 11. (62477208)
Workaround: Set SYSTEM_VERSION_COMPAT=1 in the calling environment, for example: $ SYSTEM_VERSION_COMPAT=1 legacy_script.pl

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11-beta-release-notes
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Sep 24, 2020
@ramya-rao-a ramya-rao-a added the EngSys This issue is impacting the engineering system. label Sep 25, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 25, 2020
@ghost ghost added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Sep 25, 2020
@kurtzeborn kurtzeborn added the Client This issue points to a problem in the data-plane of the library. label Sep 29, 2020
@ramya-rao-a ramya-rao-a removed the Client This issue points to a problem in the data-plane of the library. label Oct 12, 2020
@ramya-rao-a ramya-rao-a added the Client This issue points to a problem in the data-plane of the library. label Nov 11, 2020
@kurtzeborn kurtzeborn added Central-EngSys This issue is owned by the Engineering System team. and removed Client This issue points to a problem in the data-plane of the library. labels Nov 11, 2020
@praveenkuttappan
Copy link
Member

@jay-most Can you please share more details on this issue? Is the issue specific to any Azure SDK package and if yes, can you please share SDK package name and any specific steps or action that triggered this issue? If this is an in general issue in Rush multi project tool then this must be moved to rushstack repo instead of azure-sdk-for-js.

@ramya-rao-a ramya-rao-a removed the EngSys This issue is impacting the engineering system. label Nov 19, 2020
@ramya-rao-a ramya-rao-a added the needs-author-feedback Workflow: More information is needed from author to address the issue. label Dec 2, 2020
@ghost ghost removed the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Dec 2, 2020
@ramya-rao-a
Copy link
Contributor

@jay-most Closing this issue as we have not heard back from you with answers to the above questions. If you still see this problem, please log a new issue with details for questions from @praveenkuttappan above.

This was referenced Dec 15, 2021
Open
Open
@Manny27nyc Manny27nyc mentioned this issue Apr 27, 2022
Open
@snyk-bot snyk-bot mentioned this issue Apr 27, 2022
Open
@Manny27nyc Manny27nyc mentioned this issue May 14, 2022
Open
@snyk-bot snyk-bot mentioned this issue May 14, 2022
Open
@Manny27nyc Manny27nyc mentioned this issue Jun 22, 2022
Open
@Manny27nyc Manny27nyc mentioned this issue Oct 26, 2022
Open
@snyk-bot snyk-bot mentioned this issue Oct 26, 2022
Open
@Manny27nyc Manny27nyc mentioned this issue Nov 4, 2022
Open
@Manny27nyc Manny27nyc mentioned this issue Nov 5, 2022
Open
This was referenced Nov 16, 2022
Open
Open
@Manny27nyc Manny27nyc mentioned this issue Nov 29, 2022
Open
@snyk-bot snyk-bot mentioned this issue Nov 29, 2022
Open
This was referenced Dec 25, 2022
Open
Open
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@praveenkuttappan praveenkuttappan

Labels
Central-EngSys This issue is owned by the Engineering System team. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-author-feedback Workflow: More information is needed from author to address the issue. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@daviwil @ramya-rao-a @kurtzeborn @praveenkuttappan @jay-most