review-notebook-app[bot]
commented
4 months ago Check out this pull request on 
See visual diffs & provide feedback on Jupyter Notebooks.
Powered by ReviewNB
Open olachinkei opened 4 months ago
review-notebook-app[bot]
commented
4 months ago Check out this pull request on
See visual diffs & provide feedback on Jupyter Notebooks.
Powered by ReviewNB
github-actions[bot]
commented
4 months ago Thanks for contributing to wandb/examples!
We appreciate your efforts in opening a PR for the examples repository. Our goal is to ensure a smooth and enjoyable experience for you 😎.
The examples repo is regularly tested against the ever-evolving ML stack. To facilitate our work, please adhere to the following guidelines:
Notebook naming: You can use a combination of snakecase and CamelCase for your notebook name. Avoid using spaces (replace them with `) and special characters (&%$?`). For example:
Cool_Keras_integration_example_with_weights_and_biases.ipynb is acceptable, but
Cool Keras Example with W&B.ipynbis not. Avoid spaces and the & character. To refer to W&B, you can use: weights_and_biases or just wandb (it's our library, after all!)
Managing dependencies within the notebook: You may need to set up dependencies to ensure that your code works. Please avoid the following practices:
Dockerfile to the wandb/examples/examples folder (where non-Colab examples reside).pip install as the primary method to install packages. When calling pip in a cell, avoid performing other tasks. We automatically filter these types of cells, and executing other actions might break the automatic testing of the notebooks. For example,
pip install -qU wandb transformers gpt4is acceptable, but
pip install -qU wandb
import wandbis not.
GitHub, did you know that you can install them like this:!pip install -q git+https://github.com/huggingface/transformersYou don't need to clone, then
cdinto the repo and install it in editable mode.
/content directory where everything resides. Avoid explicitly referencing this directory because we test our notebooks with pure Jupyter (without Colab). Instead, use relative paths to make the notebook reproducible.The Jupyter notebook file .ipynb is nothing more than a JSON file with primarily two types of cells: markdown and code. There is also a bunch of other metadata specific to Google Colab. We have a set of tools to ensure proper notebook formatting. These tools can be found at wandb/nb_helpers.
Before merging, wait for a maintainer to
cleanand format the notebooks you're adding. You can tag @tcapelle.
The following colabs were changed -colabs/llm-finetuning-handson/Alpaca_finetunning_with_WandB.ipynb
socket-security[bot]
commented
4 months ago New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
socket-security[bot]
commented
4 months ago 🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎
To accept the risk, merge this PR and you will not be notified again.
Contains a high severity Common Vulnerability and Exposure (CVE).
Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Contains a Critical Common Vulnerability and Exposure (CVE).
Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Take 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.
If 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.
To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore pypi/jupyter-lsp@2.2.0@SocketSecurity ignore pypi/pyarrow@13.0.0@SocketSecurity ignore pypi/cryptography@41.0.4@SocketSecurity ignore pypi/aiohttp@3.8.6@SocketSecurity ignore pypi/jupyterlab@4.0.7@SocketSecurity ignore pypi/notebook@7.0.6@SocketSecurity ignore pypi/jupyterhub@4.0.2@SocketSecurity ignore pypi/jupyter-server-proxy@4.1.0
add llm finetuning handson example