Skip to content

fix: ModelBuilder assumes every ModelPackage was from JumpStart#5719

Merged
mollyheamazon merged 1 commit intoaws:masterfrom
bobbywlindsey:master
Apr 7, 2026
Merged

fix: ModelBuilder assumes every ModelPackage was from JumpStart#5719
mollyheamazon merged 1 commit intoaws:masterfrom
bobbywlindsey:master

Conversation

@bobbywlindsey
Copy link
Copy Markdown
Contributor

@bobbywlindsey bobbywlindsey commented Apr 6, 2026

Issue #, if available:

Description of changes:

ModelBuilder for model customization is too broad; it assumes every ModelPackage is a JumpStart fine-tuned model with a base_model reference. This fails for use cases where you might have trained/fine-tuned a model using a 1P image or custom container with no direct link to a base model.

I've included a base_model check so that _fetch_and_cache_recipe_config() is only called when a base_model exists.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@bobbywlindsey bobbywlindsey changed the title Fix ModelBuilder so that it doesn't assume every ModelPackage was from JumpStart fix: ModelBuilder so that it doesn't assume every ModelPackage was from JumpStart Apr 6, 2026
@bobbywlindsey bobbywlindsey changed the title fix: ModelBuilder so that it doesn't assume every ModelPackage was from JumpStart fix: ModelBuilder assumes every ModelPackage was from JumpStart Apr 6, 2026
@mollyheamazon mollyheamazon merged commit 272fdbf into aws:master Apr 7, 2026
15 of 17 checks passed
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