Skip to content

Supabase (self-hosted): Reproduce High-Severity Failures from the Troubleshooting Guide & Write a CRE Rule [Submit by September 3 11:59 pm ET] #131

@Lyndon-prequel

Description

@Lyndon-prequel

Exclusive

⭐ star these repos and be the first to see new bounties

Turn a manual troubleshooting guide into a library of CREs

We have a technical guide that walks through a specific set of reliability issues. Your task is to reproduce the issues and break them down into a structured set of CREs that can be shared with the community and used by preq to automate problem detection.

This a great opportunity to get hands-on experience with increasingly popular technologies.

📌 What you’ll do

  • Read the guides
  • Pick at least 10 issues to reproduce
  • Extract and document multiple CREs based on the key failure modes, signals, and remediations described
  • Submit them in the Prequel CRE format following the structure of this repo.

✅ What we’re looking for

  • At least 10 high-quality CREs with reproductions

🏆 Award

$300 if the submission hits all criteria

⚙️ Process

  • We'll leave this bounty unassigned for 3 days. We encourage anyone interested to comment /attempt Istio Ambient Troubleshooting Rules #81 on the issue
  • We will then assign the bounty to a someone based on
    • quality of plan
    • past contributions
      ** The assignee will have 5 days to exclusively pursue the bounty. If the work is not completed, the bounty may be reassigned **

You must:

  1. Reproduce the failure scenarios
  2. Share a minimal, working reproductions (e.g., Helm, Docker Compose, etc.)
  3. Write unique CRE-format detection rules for preq
  4. Install preq and run the rules

📦 Deliverables:

  • Reproduction setup and clear README
  • Link to your rules in seperate CRE playgrounds
  • PR containing
    • the new CRE rules
    • example logs in test.log files
    • updated tags.yaml and category.yaml files
    • updated data-sources.yaml file
  • Demo video of
    • your reproductions
    • running the rules

📅 Deadline

Will be assigned by Aug 29
Submit your pull request by Submit by September 3 11:59 pm ET

Questions? Open a discussion or find us on slack. Happy hunting!

/bounty 300

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions