[GSK-1888] Avoid to send nullable values in callable from ML worker to Backend #1503
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.








Description
Add a pre-check in ML worker for Database constraints, referring to:
ai.giskard.domain.Callableai.giskard.domain.TestFunctionai.giskard.domain.DatasetProcessFunctionai.giskard.domain.SlicingFunctionai.giskard.domain.TransformationFunctionSo that the badly-made callable functions will not be sent to the backend (pydantic will raise an error).
Related Issue
[GSK-1888] Code for callable functions becomes NULL
Type of Change
Checklist
CODE_OF_CONDUCT.mddocument.CONTRIBUTING.mdguide.make codestyle.