Skip to content
This repository was archived by the owner on May 23, 2024. It is now read-only.
This repository was archived by the owner on May 23, 2024. It is now read-only.

Pre-Postprocessing feature seems to not work anymore. #212

Description

@flacout

Bug Description
Hello,
I built the image from the latest commit: 6a51a60
I pushed it in ECR and deployed a multi-model Sagemaker endpoint. The endpoint is working well for a simple model, but when I try to upload a model that contain code/inference.py, the new model cannot load the input and output handlers and therefore return an input error when I call the model.

I tried to built a previous version: commit: 3bab56e "change: update MME Pre/Post-Processing model and script paths (#153)" when the feature of pre-postprocessing was first introduce to the container, and this time it works perfectly. I can deploy models with code/inference.py, install new pip packages with the code/requirement.txt and add local python modules in the code/lib folder.

It seems to me that this feature of having models with independent pre-postprocessing capability was lost somehow in the latest commits of this repository, is this something intentional, or it was an error of manipulation, or am I missing something?

To reproduce
The model directory structure I used looks like this, following the readme guidelines:

|--[model_version_number]
    |--assets
    |--variables
    |--saved_model.pb
|--code
    |--lib
        |--external_module
    |--inference.py

For the inference.py I used the implement of handler instead of the input_handler and output_handler pair.

Thanks
Fabrice

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions