Skip to content

Support passing metadata to cheval annotators.#1553

Merged
superdosh merged 5 commits into
mainfrom
security-metadata-support
Jun 24, 2026
Merged

Support passing metadata to cheval annotators.#1553
superdosh merged 5 commits into
mainfrom
security-metadata-support

Conversation

@superdosh

@superdosh superdosh commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@superdosh superdosh temporarily deployed to Scheduled Testing June 24, 2026 17:04 — with GitHub Actions Inactive
@github-actions

Copy link
Copy Markdown

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

@superdosh superdosh marked this pull request as ready for review June 24, 2026 17:10
@superdosh superdosh requested a review from a team as a code owner June 24, 2026 17:10

@bkorycki bkorycki left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks good! But why do we need to update both the ChevalAnnotator and DagAnnotator? Are they both used by security?

@rogthefrog rogthefrog left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

👍🏻

@superdosh

Copy link
Copy Markdown
Contributor Author

Looks good! But why do we need to update both the ChevalAnnotator and DagAnnotator? Are they both used by security?

ChevalAnnotator makes sure the request sent by modelbench to cheval has the metadata. Then the change to DAGAnnotator is used within cheval to make sure the metadata is read into the EvalContext.

@bkorycki

@bkorycki

Copy link
Copy Markdown
Contributor

@superdosh That makes sense!

@wpietri wpietri left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think this is going the wrong direction in a way that makes the domain model muddier and harder to maintain. If it's something we need to do for expediency, go for it, but please add a card for doing it right that we tackle as soon as the emergency is past.

Comment thread src/modelgauge/annotators/cheval/request.py Outdated
Comment thread src/modelgauge/annotators/cheval/annotator.py Outdated
Comment thread src/modelgauge/annotators/cheval/request.py Outdated
Comment thread src/modelgauge/prompt.py Outdated
@superdosh

Copy link
Copy Markdown
Contributor Author

I think this is going the wrong direction in a way that makes the domain model muddier and harder to maintain. If it's something we need to do for expediency, go for it, but please add a card for doing it right that we tackle as soon as the emergency is past.

@wpietri I think there's a few changes I can make quickly that should alleviate many of the concerns. Will do a quick update / test and then ping you!

@superdosh superdosh force-pushed the security-metadata-support branch from d29f8e8 to 7ccdaae Compare June 24, 2026 20:03

@wpietri wpietri left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This makes the problem clearer, which I think is a good step forward, but let's definitely come back to clean this up when we're past the rush.

@superdosh superdosh temporarily deployed to Scheduled Testing June 24, 2026 20:13 — with GitHub Actions Inactive
@superdosh superdosh temporarily deployed to Scheduled Testing June 24, 2026 20:18 — with GitHub Actions Inactive
@superdosh

Copy link
Copy Markdown
Contributor Author

This makes the problem clearer, which I think is a good step forward, but let's definitely come back to clean this up when we're past the rush.

Added #1555 with details as follow up!

@superdosh superdosh merged commit 7977568 into main Jun 24, 2026
3 checks passed
@superdosh superdosh deleted the security-metadata-support branch June 24, 2026 20:40
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 24, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants