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

Cannot build due to pyyaml-6.0 errors #306

Closed
nitrocode opened this issue Aug 17, 2023 · 0 comments · Fixed by #310
Closed

Cannot build due to pyyaml-6.0 errors #306

nitrocode opened this issue Aug 17, 2023 · 0 comments · Fixed by #310

Comments

@nitrocode
Copy link
Contributor

Issue

I ran the following (as per docs)

brew tap salesforce/cloudsplaining https://github.com/salesforce/cloudsplaining
brew install cloudsplaining
and get this error
Last 15 lines from /Users/user/Library/Logs/Homebrew/cloudsplaining/19.python3:

  note: This error originates from a subprocess, and is likely not a problem with pip.
  full command: /opt/homebrew/Cellar/cloudsplaining/0.5.2/libexec/bin/python /opt/homebrew/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py get_requires_for_build_wheel /private/tmp/tmpvn0roiex
  cwd: /private/tmp/cloudsplaining--PyYAML-20230817-13520-19n0g16/PyYAML-6.0
  Getting requirements to build wheel: finished with status 'error'
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

[notice] A new release of pip is available: 23.0.1 -> 23.2.1
[notice] To update, run: python -m pip install --upgrade pip

If reporting this issue please do so to (not Homebrew/brew or Homebrew/homebrew-core):
  salesforce/cloudsplaining

/opt/homebrew/Library/Homebrew/utils/github/api.rb:337:in `raise_error': Validation Failed: [{"message"=>"The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them.", "resource"=>"Search", "field"=>"q", "code"=>"invalid"}] (GitHub::API::ValidationFailedError)
	from /opt/homebrew/Library/Homebrew/utils/github/api.rb:263:in `open_rest'
	from /opt/homebrew/Library/Homebrew/utils/github.rb:178:in `search'
	from /opt/homebrew/Library/Homebrew/utils/github.rb:182:in `search_results_items'
	from /opt/homebrew/Library/Homebrew/utils/github.rb:36:in `search_issues'
	from /opt/homebrew/Library/Homebrew/utils/github.rb:62:in `issues_for_formula'
	from /opt/homebrew/Library/Homebrew/exceptions.rb:502:in `fetch_issues'
	from /opt/homebrew/Library/Homebrew/exceptions.rb:497:in `issues'
	from /opt/homebrew/Library/Homebrew/exceptions.rb:553:in `dump'
	from /opt/homebrew/Library/Homebrew/brew.rb:151:in `rescue in <main>'
	from /opt/homebrew/Library/Homebrew/brew.rb:139:in `<main>'
/opt/homebrew/Library/Homebrew/formula.rb:2741:in `block in system': Failed executing: python3 -m pip --python=/opt/homebrew/Cellar/cloudsplaining/0.5.2/libexec/bin/python install --verbose --no-deps --no-binary=:all: --ignore-installed --use-feature=no-binary-enable-wheel-cache --no-compile /private/tmp/cloudsplaining--PyYAML-20230817-13520-19n0g16/PyYAML-6.0 (BuildError)
	from /opt/homebrew/Library/Homebrew/formula.rb:2677:in `open'
	from /opt/homebrew/Library/Homebrew/formula.rb:2677:in `system'
	from /opt/homebrew/Library/Homebrew/language/python.rb:313:in `do_install'
	from /opt/homebrew/Library/Homebrew/language/python.rb:277:in `block (2 levels) in pip_install'
	from /opt/homebrew/Library/Homebrew/resource.rb:128:in `block (2 levels) in unpack'
	from /opt/homebrew/Library/Homebrew/download_strategy.rb:118:in `chdir'
	from /opt/homebrew/Library/Homebrew/download_strategy.rb:118:in `chdir'
	from /opt/homebrew/Library/Homebrew/download_strategy.rb:105:in `stage'

I get a similar error when attempting to install policy_sentry.

This workaround also failed

echo 'Cython < 3.0' > /tmp/constraint.txt
PIP_CONSTRAINT=/tmp/constraint.txt brew install cloudsplaining

References

This was referenced Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant