You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When user pass non-default config in processor, and the non-default config is in expected_types_and_attributes check, and set enforce_consistency=True, the pipeline will fail.
If we create a Pipeline, with config = {"entry_type": "ft.onto.base_ontology.Sentence"} but not default Document, the pipeline will fail with
forte.common.exception.ExpectedRecordNotFound: The record type ft.onto.base_ontology.Document is not found in meta of the prediction datapack.
Expected behavior
It should record the config with no error.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
OS: [e.g. iOS]
Version [e.g. 22]
Python and Package verions: [e.g. Python version, Pytorch version]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
When user pass non-default config in processor, and the non-default config is in expected_types_and_attributes check, and set enforce_consistency=True, the pipeline will fail.
To Reproduce
Steps to reproduce the behavior:
Use QuestionAnsweringSingle Processor as an example. https://github.com/asyml/forte-wrappers/blob/main/src/huggingface/forte/huggingface/question_and_answering_single.py
If we create a Pipeline, with config = {"entry_type": "ft.onto.base_ontology.Sentence"} but not default Document, the pipeline will fail with
forte.common.exception.ExpectedRecordNotFound: The record type ft.onto.base_ontology.Document is not found in meta of the prediction datapack.
Expected behavior
It should record the config with no error.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: