operatorai / operatorai/modelstore
ValueError: could not find matching manager
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 403
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
I am trying to run the following code using v0.0.80
import tensorflow as tf
from modelstore import ModelStore
model_store = ModelStore.from_azure(
container_name="xyz",
root_prefix="xyz",
)
def tf_model():
model = tf.keras.models.Sequential(
[
tf.keras.layers.Dense(5, activation="relu", input_shape=(10,)),
tf.keras.layers.Dropout(0.2),
tf.keras.layers.Dense(1),
]
)
model.compile(optimizer="adam", loss="mean_squared_error")
return model
# Upload model
model = tf_model()
meta_data = model_store.upload(model_domain, model=model)
I get the following error:
Traceback (most recent call last):
File "/tmp/core/trainer.py", line 140, in <module>
meta_data = model_store.upload(model_domain, model=model)
File "/tmp/.venv/lib/python3.10/site-packages/modelstore/model_store.py", line 283, in upload
managers = matching_managers(self._libraries, **kwargs)
File "/tmp/.venv/lib/python3.10/site-packages/modelstore/models/managers.py", line 87, in matching_managers
raise ValueError("could not find matching manager")
ValueError: could not find matching manager
When I tried to log all the managers in this function: https://github.com/operatorai/modelstore/blob/6e438c55d90fad1b5a0a80d278ef2f24f26c93b4/modelstore/models/managers.py#L80
I get this:
[<modelstore.models.missing_manager.MissingDepManager object at 0x12da03610>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da03d60>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da34ee0>, <modelstore.models.model_file.ModelFileManager object at 0x12da34940>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da34a30>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da348e0>, <modelstore.models.missing_manager.MissingDepManager object at 0x12d44df00>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da34b80>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da34ac0>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da34970>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da34bb0>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da34be0>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da347f0>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da34e80>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da34e20>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da34dc0>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da34d60>, <modelstore.models.missing_manager.MissingDepManager object at 0x12da34d00>]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at modelstore/model_store.py in ModelStore.upload and modelstore/models/managers.py in matching_managers, then reproduce the v0.0.80 example with its listed dependencies. Compare the available managers and MissingDepManager entries to identify why no manager matches; done means the TensorFlow model upload no longer raises this ValueError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python, tensorflow
- Domain
- cloud, machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100