[KEY] remove accidental key

[mayank31398]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @mayank31398, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical security oversight by eliminating sensitive API key information that was inadvertently committed directly into a shell script. The change ensures that API keys are no longer hardcoded, thereby enhancing security posture and mitigating the risk of unauthorized access or misuse of the Weights & Biases service.

Highlights

• Security Fix: Removed the hardcoded WANDB_API_KEY and WANDB_BASE_URL environment variables from scripts/prime-intellect/pretrain-job.sh to prevent accidental exposure of sensitive credentials.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• scripts/prime-intellect/pretrain-job.sh
  • Removed WANDB_API_KEY environment variable export.
  • Removed WANDB_BASE_URL environment variable export.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly removes a hardcoded WANDB_API_KEY from the pretrain-job.sh script. This is an important security fix. My review includes a critical comment emphasizing the necessary follow-up actions, such as revoking the compromised key and cleaning the git history, to fully mitigate the security risk.

I am having trouble creating individual review comments. Click here to see my feedback.

scripts/prime-intellect/pretrain-job.sh (75-76)

Thank you for removing the hardcoded WANDB_API_KEY. This is a critical security issue. Since this key has been committed to the repository, it must be considered compromised. Please take the following actions immediately:

1. Revoke the key: The exposed WANDB_API_KEY should be revoked immediately in your Weights & Biases account settings to prevent any potential misuse.
2. Scrub git history: The repository's history should be scrubbed to remove any trace of this key. Tools like git-filter-repo or BFG Repo-Cleaner can be used for this. This is crucial to ensure the secret is not present in previous commits.