A fast, easy-to-use, production-ready inference server for computer vision supporting deployment of many popular model architectures and fine-tuned models.
This is the preview of custom python code block in workflows - so far implemented quite ugly - but showcasing what will be possible.
Methodology:
new optional entry in workflow definition with dynamic blocks
dynamic blocks configurable via JSON definition (manifest + code)
once compiled - dynamic block becomes standard block with minor limitations (no init parameters from EE, but possible to define init() function to define state)
dynamic blocks can be instantiated as any other block in "steps" list
proven with tests that steps works nicely with other blocks, including flow-control
disabled completely at hosted platform (proven by tests) - both compilation and execution!
new endpoint POST /workflows/blocks/describe which takes optional payload with list of blocks - once it is done -dynamic blocks schemas and connections are generated into output -
old, parameter-free GET /workflows/blocks/describe remained, yet deprecated to be removed later
GET /workflows/blocks/describe and POST /workflows/blocks/describe will return OpenAPI schema for manifest of dynamic block
Type of change
Please delete options that are not relevant.
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update
How has this change been tested, please provide a testcase or example of how you tested the change?
Old CI still green 🟢
new unit tests
new integration tests (workflows, hosted-inference, inference sever)
Any specific deployment considerations
POST endpoint for workflows must be exposed by gateway (already submitted infra PR)
Description
This is the preview of custom python code block in
workflows- so far implemented quite ugly - but showcasing what will be possible.Methodology:
init()function to define state)"steps"listPOST /workflows/blocks/describewhich takes optional payload with list of blocks - once it is done -dynamic blocks schemas and connections are generated into output -GET /workflows/blocks/describeremained, yet deprecated to be removed laterGET /workflows/blocks/describeandPOST /workflows/blocks/describewill return OpenAPI schema for manifest of dynamic blockType of change
Please delete options that are not relevant.
How has this change been tested, please provide a testcase or example of how you tested the change?
Any specific deployment considerations
Docs