Skip to content

chore: retire pandamonium #5122

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

sklein12
Copy link
Contributor

No description provided.

Copy link
Contributor

gru-agent bot commented Jul 30, 2025

TestGru Assignment

Summary

Link CommitId Status Reason
Detail 2e76d48 ✅ Finished

History Assignment

Files

File Pull Request
src/redteam/strategies/index.ts ❌ Failed (All Jest unit tests in test/redteam/strategies/index.test.ts passed successfully. The only failures reported are from ESLint, which is due to a missing ESLint configuration file (eslint.config.js) and not due to a bug in the source code. The code changes (removal of the 'pandamonium' strategy) are not covered by any failing test, and the test suite does not expect this strategy to exist. Therefore, the job did not fail due to a source code bug.)
src/redteam/constants/strategies.ts ❌ Failed (All Jest unit tests passed with 100% coverage, and TypeScript compilation succeeded. The only failures are from ESLint, which is due to a missing ESLint configuration file (eslint.config.js) after upgrading to ESLint v9, not a source code bug. The test job is marked as failed because of this environment/configuration issue, not due to a bug in the source code.)
src/redteam/constants/metadata.ts ❌ Failed (All unit tests passed successfully, as indicated by the jest output. The only failure was from ESLint, which is due to a missing ESLint configuration file (eslint.config.js) and not a bug in the source code. The code changes (removal of 'pandamonium' keys from several constant objects) are consistent and do not break any tests. Therefore, the job did not fail due to a source code bug.)
src/redteam/constants/frameworks.ts ❌ Failed (All Jest unit tests passed successfully, and TypeScript compilation also passed. The only failure was from ESLint, which is due to a missing ESLint configuration file (eslint.config.js) in the environment, not a bug in the source code. The code and tests are correct.)

Tip

You can @gru-agent and leave your feedback. TestGru will make adjustments based on your input

Copy link
Contributor

coderabbitai bot commented Jul 30, 2025

📝 Walkthrough

Walkthrough

This change set removes all code, documentation, configuration, tests, and UI elements related to the "Pandamonium" red teaming strategy from the project. The deletion encompasses the provider implementation, strategy logic, metadata, configuration schema entries, UI components, and related documentation. All references to "Pandamonium" are eliminated from source files, constants, sidebars, and test suites. The removal also includes the provider registration, strategy arrays, and associated test and utility files, ensuring that the "Pandamonium" strategy is no longer available or referenced anywhere in the codebase or documentation.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~40 minutes

  • Complexity: The removal spans multiple subsystems (provider, strategies, UI, config, tests, docs), with several files deleted and many others updated for reference removal. Review requires careful attention to ensure no lingering references or regressions in related functionality.

Suggested reviewers

  • mldangelo

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch steve/07302025-removepandamonium

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3a4542b and 2e76d48.

📒 Files selected for processing (21)
  • site/docs/_shared/data/strategies.ts (0 hunks)
  • site/docs/red-team/strategies/pandamonium.md (0 hunks)
  • site/sidebars.js (0 hunks)
  • site/static/config-schema.json (1 hunks)
  • src/app/src/pages/redteam/setup/components/StrategyConfigDialog.tsx (0 hunks)
  • src/app/src/pages/redteam/setup/components/strategies/StrategyItem.test.tsx (0 hunks)
  • src/app/src/pages/redteam/setup/components/strategies/StrategyItem.tsx (0 hunks)
  • src/app/src/pages/redteam/setup/components/strategies/utils.ts (0 hunks)
  • src/evaluator.ts (0 hunks)
  • src/providers/registry.ts (0 hunks)
  • src/redteam/constants/frameworks.ts (0 hunks)
  • src/redteam/constants/metadata.ts (0 hunks)
  • src/redteam/constants/strategies.ts (0 hunks)
  • src/redteam/providers/pandamonium.ts (0 hunks)
  • src/redteam/strategies/index.ts (0 hunks)
  • src/redteam/strategies/pandamonium.ts (0 hunks)
  • src/types/index.ts (0 hunks)
  • test/providers/registry.test.ts (0 hunks)
  • test/redteam/constants/strategies.test.ts (0 hunks)
  • test/redteam/providers/pandamonium.test.ts (0 hunks)
  • test/redteam/strategies/strategyId.test.ts (0 hunks)
💤 Files with no reviewable changes (20)
  • test/redteam/strategies/strategyId.test.ts
  • src/app/src/pages/redteam/setup/components/strategies/StrategyItem.tsx
  • site/sidebars.js
  • src/app/src/pages/redteam/setup/components/strategies/utils.ts
  • site/docs/_shared/data/strategies.ts
  • src/redteam/constants/frameworks.ts
  • src/types/index.ts
  • src/app/src/pages/redteam/setup/components/StrategyConfigDialog.tsx
  • src/app/src/pages/redteam/setup/components/strategies/StrategyItem.test.tsx
  • test/redteam/constants/strategies.test.ts
  • src/evaluator.ts
  • site/docs/red-team/strategies/pandamonium.md
  • src/redteam/strategies/pandamonium.ts
  • test/providers/registry.test.ts
  • src/providers/registry.ts
  • src/redteam/constants/strategies.ts
  • src/redteam/strategies/index.ts
  • test/redteam/providers/pandamonium.test.ts
  • src/redteam/constants/metadata.ts
  • src/redteam/providers/pandamonium.ts
🧰 Additional context used
📓 Path-based instructions (2)
{site/**,examples/**}

📄 CodeRabbit Inference Engine (.cursor/rules/gh-cli-workflow.mdc)

Any pull request that only touches files in 'site/' or 'examples/' directories must use the 'docs:' prefix in the PR title, not 'feat:' or 'fix:'

Files:

  • site/static/config-schema.json
site/**

📄 CodeRabbit Inference Engine (.cursor/rules/gh-cli-workflow.mdc)

If the change is a feature, update the relevant documentation under 'site/'

Files:

  • site/static/config-schema.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (20)
  • GitHub Check: webui tests
  • GitHub Check: Share Test
  • GitHub Check: Test on Node 20.x and windows-latest
  • GitHub Check: Test on Node 20.x and macOS-latest
  • GitHub Check: Redteam Custom Enterprise Server
  • GitHub Check: Redteam
  • GitHub Check: Test on Node 24.x and ubuntu-latest
  • GitHub Check: Test on Node 22.x and macOS-latest
  • GitHub Check: Test on Node 24.x and macOS-latest
  • GitHub Check: Test on Node 18.x and macOS-latest
  • GitHub Check: Test on Node 18.x and windows-latest
  • GitHub Check: Test on Node 20.x and ubuntu-latest
  • GitHub Check: Test on Node 22.x and ubuntu-latest
  • GitHub Check: Test on Node 18.x and ubuntu-latest
  • GitHub Check: Build on Node 22.x
  • GitHub Check: Build Docs
  • GitHub Check: Build on Node 20.x
  • GitHub Check: Build on Node 18.x
  • GitHub Check: Build on Node 24.x
  • GitHub Check: Analyze (javascript-typescript)

Comment on lines +1542 to 1544
"description": "Strategies to use for redteam generation.\n\nDefaults to basic, jailbreak, jailbreak:composite\nSupports audio, base64, basic, best-of-n, camelcase, citation, crescendo, custom, default, emoji, gcg, goat, hex, homoglyph, image, jailbreak, jailbreak:composite, jailbreak:likert, jailbreak:tree, leetspeak, math-prompt, mischievous-user, morse, multilingual, other-encodings, piglatin, prompt-injection, retry, rot13, video",
"default": ["default"]
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Description–default mismatch: default property ≠ described defaults

The description still states that basic, jailbreak, jailbreak:composite are the defaults, yet the "default" value declared two dozen lines above is ["default"]. Either:

  1. Update the description to reflect that the sole default is "default" (which the codebase later expands internally), or
  2. Change the "default" array at Line 1474 to ["basic", "jailbreak", "jailbreak:composite"].

Diff for option 1 (minimal):

-Defaults to basic, jailbreak, jailbreak:composite
+Defaults to "default" (which internally expands to basic, jailbreak, and jailbreak:composite)

Keeping schema docs accurate prevents confusion for integrators and tooling that rely on the JSON-schema comments.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"description": "Strategies to use for redteam generation.\n\nDefaults to basic, jailbreak, jailbreak:composite\nSupports audio, base64, basic, best-of-n, camelcase, citation, crescendo, custom, default, emoji, gcg, goat, hex, homoglyph, image, jailbreak, jailbreak:composite, jailbreak:likert, jailbreak:tree, leetspeak, math-prompt, mischievous-user, morse, multilingual, other-encodings, piglatin, prompt-injection, retry, rot13, video",
"default": ["default"]
},
"description": "Strategies to use for redteam generation.\n\nDefaults to \"default\" (which internally expands to basic, jailbreak, and jailbreak:composite)\nSupports audio, base64, basic, best-of-n, camelcase, citation, crescendo, custom, default, emoji, gcg, goat, hex, homoglyph, image, jailbreak, jailbreak:composite, jailbreak:likert, jailbreak:tree, leetspeak, math-prompt, mischievous-user, morse, multilingual, other-encodings, piglatin, prompt-injection, retry, rot13, video",
"default": ["default"]
🤖 Prompt for AI Agents
In site/static/config-schema.json around lines 1542 to 1544, the description of
default strategies lists "basic, jailbreak, jailbreak:composite" as defaults,
but the actual "default" property set earlier is ["default"]. To fix this
mismatch, either update the description to state that the sole default is
"default" or change the "default" property at line 1474 to ["basic",
"jailbreak", "jailbreak:composite"] so it matches the description. Choose one
approach and ensure both the description and default property are consistent.

Copy link
Member

@mldangelo mldangelo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens when someone specifies this in a config? Would be great to look at the PRs that introduced this and see if any other simplifications can be made. I remember modifying a few types.

@@ -148,7 +148,6 @@ export interface RunEvalOptions {
registers?: EvalRegisters;
isRedteam: boolean;

// Used by pandamonium, this should never be passed to callApi, it could be a massive object that will break the stack
allTests?: RunEvalOptions[];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we still need these?

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 this pull request may close these issues.

2 participants