You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0d811b2
Browse filesBrowse the repository at this point in the historyBrowse files
Rohan Gujarathi
committed
fix: propagate user-supplied tags to created resources
Tags passed to the trainer and evaluator classes were accepted but never
reached the resources they create, so they could not be used for tag-based
resource association.
- Trainers (SFT, DPO, RLVR, RLAIF, MultiTurnRL): the serverless train() path
built its tag list from the JumpStart tags only and discarded self.tags.
MultiTurnRLTrainer additionally computed tags and then never passed them to
Job.create().
- BaseTrainer._train_serverful_smtj() did not forward tags to
ModelTrainer.from_recipe().
- BaseEvaluator had no tags field at all; add one and merge it into the
pipeline tags.
- MultiTurnRLEvaluator passed only the evaluation discovery tag to
CreatePipeline and dropped customer tags.
The create APIs are typed List[Tag] and validated by pydantic, which coerces
plain key/value dicts and accepts Tag objects, so the merged tag lists are
passed through as-is. MultiTurnRLEvaluator is the exception: it calls
CreatePipeline through raw boto3 and also renders tags into the pipeline
definition, both of which require the capitalized Key/Value form, so its
tags are normalized locally.
0 commit comments