rstudio / rstudio/vetiver-python
what to do with ptype enforcement at deployment
Open
Nobody has claimed this yet.
bug
deploy
- Dominant language
- Python
- Stars
- 71
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Currently, if you save a VetiverModel() with no ptype, you can deploy with check_ptype=True with no error. This can POST to an endpoint with no error, but with certain data types, predictions come back dictionaries of errors.
I am planning on enforcing the following ⬇️
- ptype saved, deploy with ptype ✅
- ptype saved, deploy with NO ptype ❓ give warning
- NO ptype saved, deploy with ptype ❌ raise error
- NO ptype saved, deploy with NO ptype ✅
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files or tests. Start by locating the deployment path that handles check_ptype and compare its behavior with the four ptype cases listed; done means the warning, error, and success outcomes are explicit and verified for all four combinations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100