Skip to content

Handle bad requests in each backend #193

Description

@varunsh-xilinx

We need a robust strategy for handling bad requests in each backend. For example, if a request comes with the wrong data type or shape, it needs to be handled and then not passed on to the responder. What should happen if a subset of requests in a batch are bad?

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