-
Notifications
You must be signed in to change notification settings - Fork 12
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
Blue hawk demo #1197
base: main
Are you sure you want to change the base?
Blue hawk demo #1197
Conversation
Suggestions are drifting from the originating lines; added more logic to ensure the suggestions line up properly
New dependencies detected. Learn more about Socket for GitHub ↗︎
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhy is native code a concern?Contains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior. Verify that the inclusion of native code is expected and necessary for this package's functionality. If it is unnecessary or unexpected, consider using alternative packages without native code to mitigate potential risks. What is a license policy violation?This package is not allowed per your license policy. Review the package's license to ensure compliance. Find a package that does not violate your license policy or adjust your policy to allow this package's license. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
Deploying docs with
|
Latest commit: |
ff83f15
|
Status: | ✅ Deploy successful! |
Preview URL: | https://2925e4d9.docodile.pages.dev |
Branch Preview URL: | https://blue-hawk-demo.docodile.pages.dev |
@@ -13,7 +13,7 @@ jobs: | |||
- name: Find Python scripts | |||
id: list-scripts | |||
run: | | |||
SCRIPTS=$(find scripts -name "*.py" | jq -R -s -c 'split("\n")[:-1]') | |||
SCRIPTS=$(find code_examples/source -name "*.py" | jq -R -s -c 'split("\n")[:-1]') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit greedy. At a minimum I'd add -type f
so you don't find directories that end in .py
. I'm also confused why you have to take something that is going to be multi-line input with one result per line, join it up, and then split it again right away?
SCRIPTS=$(find code_examples/source -name "*.py" | jq -R -s -c 'split("\n")[:-1]') | |
SCRIPTS=$(find 'code_examples/source' -type f -name "*.py" | jq -R -s -c 'split("\n")[:-1]') |
quickstart.py
:Where
quickstart
refers to the file name andall
refers to the code block comment + titleThis PR also adds a GitHub Action that checks:
check_dependencies.sh
code_examples/source
run successfully. It usesmatrix
to check files in parallel.This is a WIP PR. Not ready for reviews just yet while I still demo, configure.
Known to-dos:
wandb
API key for checks. See this line in error message.