Skip to content
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

[AGENT-6788] Prompt could be in the form of list #1285

Merged
merged 2 commits into from
Feb 20, 2025

Conversation

amarmudrankit
Copy link
Contributor

For chat api, the prompt could be in the form of list. Make sure to serialize it before reporting for monitoring

This repository is public. Do not put here any private DataRobot or customer's data: code, datasets, model artifacts, .etc.

Summary

Rationale

For chat api, the prompt could be in the form of list.  Make
sure to serialize it before reporting for monitoring
@engprod-2
Copy link

engprod-2 bot commented Feb 19, 2025

The Needs Review labels were added based on the following file changes.

Team @datarobot/core-modeling (#core-modeling) was assigned because of changes in files:

custom_model_runner/datarobot_drum/drum/language_predictors/base_language_predictor.py

Team @datarobot/custom-models (#custom-models) was assigned because of changes in files:

custom_model_runner/datarobot_drum/drum/language_predictors/base_language_predictor.py
tests/unit/datarobot_drum/drum/language_predictors/test_base_language_predictor.py

If you think that there are some issues with ownership, please discuss with C&A domain at #sdtk slack channel and create PR to update DRCODEOWNERS\CODEOWNERS file.

concatenated_prompt.append(message)
latest_message = "\n".join(concatenated_prompt)
else:
logger.warning(f"Unhandled prompt type: {type(prompt_content)}")
Copy link
Member

Choose a reason for hiding this comment

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

Should we also consider sending an MLOps event because this message will only be visible in the model log. This probably requires more thought (as would we spam our platform with events for a poorly configured model?)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, it needs more thought.

I think sending event will be little too expensive - because in case of series of wrong prompts - it will fill up events table. This is model monitoring not able to understand the type and not the model. So, if model is misconfigured, user would know the error right away. In case of monitoring - we can try to deduplicate the events and send only 1 event for 1 unhandled type. I will create an improvement ticket but not sure if we will be able to work on it by 11.0

Copy link

@orgie77 orgie77 left a comment

Choose a reason for hiding this comment

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

LGTM

@engprod-2
Copy link

engprod-2 bot commented Feb 20, 2025

Label Needs Review: Custom Models was removed because @yakov-g is part of Custom Models domain.

@amarmudrankit amarmudrankit merged commit a261243 into master Feb 20, 2025
26 checks passed
@svc-engprod-git1 svc-engprod-git1 deleted the amarmudrankit/AGENT-6788 branch February 20, 2025 17:59
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.

5 participants