ragflow
ragflow copied to clipboard
Published
1 week ago
•
infiniflow
infiniflow
[Bug]: Using the chat model provided by xinference, an error occurs when parsing the document: Invalid input. Please specify the prompt
Is there an existing issue for the same bug?
- [x] I have checked the existing issues.
RAGFlow workspace code commit ID
v0.16.0
RAGFlow image version
v0.16.0 full
Other environment information
Actual behavior
10:59:54 Task has been received.
10:59:54 Page(1~100000001): Start to parse.
10:59:54 Page(1~100000001): Finish parsing.
10:59:54 Page(1~100000001): Generate 3 chunks
10:59:56 Page(1~100000001): Embedding chunks (1.72s)
10:59:56 Page(1~100000001): Done (0.11s)
10:59:57 Start Graph Extraction
10:59:57 Task has been received.
11:00:16 Knowledge graph extraction error:**ERROR**: Error code: 400 - {'detail': 'Invalid input. Please specify the prompt.'}
11:00:16 Knowledge graph extraction error:**ERROR**: Error code: 400 - {'detail': 'Invalid input. Please specify the prompt.'}
11:00:16 Knowledge graph extraction error:**ERROR**: Error code: 400 - {'detail': 'Invalid input. Please specify the prompt.'}
11:00:16 Knowledge Graph is done (19.14s)
11:00:21 Start Graph Resolution
11:00:21 Task has been received.
11:00:22 [ERROR]Faild to fetch the graph.
11:00:22 Knowledge Graph resolution is done (0.16s)
Expected behavior
No response
Steps to reproduce
1. create dataset: enable light graph
1. upload document
2. parse document
Additional information
No response
@KevinHuSh
[{'role': 'system', 'content': '-Goal-\nGiven a text document that is potentially relevant to this activity and a list of entity types, identify all entities of those types from the text and all relationships among the identified entities.\nUse Chinese as output language.\n\n-Steps-\n1. Identify all entities. For each identified entity, extract the following information:\n- entity_name: Name of the entity, use same language as input text. If English, capitalized the name.\n- entity_type: One of the following types: [organization,person,geo,event,category]\n- entity_description: Comprehensive description of the entity\'s attributes and activities\nFormat each entity as ("entity"<|><entity_name><|><entity_type><|><entity_description>)\n\n2. From the entities identified in step 1, identify all pairs of (source_entity, target_entity) that are *clearly related* to each other.\nFor each pair of related entities, extract the following information:\n- source_entity: name of the source entity, as identified in step 1\n- target_entity: name of the target entity, as identified in step 1\n- relationship_description: explanation as to why you think the source entity and the target entity are related to each other\n- relationship_strength: a numeric score indicating strength of the relationship between the source entity and target entity\n- relationship_keywords: one or more high-level key words that summarize the overarching nature of the relationship, focusing on concepts or themes rather than specific details\nFormat each relationship as ("relationship"<|><source_entity><|><target_entity><|><relationship_description><|><relationship_keywords><|><relationship_strength>)\n\n3. Identify high-level key words that summarize the main concepts, themes, or topics of the entire text. These should capture the overarching ideas present in the document.\nFormat the content-level key words as ("content_keywords"<|><high_level_keywords>)\n\n4. Return output in Chinese as a single list of all the entities and relationships identified in steps 1 and 2. Use **##** as the list delimiter.\n\n5. When finished, output <|COMPLETE|>\n\n######################\n-Examples-\n######################\nExample 1:\n\nEntity_types: [person, technology, mission, organization, location]\nText:\nwhile Alex clenched his jaw, the buzz of frustration dull against the backdrop of Taylor\'s authoritarian certainty. It was this competitive undercurrent that kept him alert, the sense that his and Jordan\'s shared commitment to discovery was an unspoken rebellion against Cruz\'s narrowing vision of control and order.\n\nThen Taylor did something unexpected. They paused beside Jordan and, for a moment, observed the device with something akin to reverence. “If this tech can be understood..." Taylor said, their voice quieter, "It could change the game for us. For all of us.”\n\nThe underlying dismissal earlier seemed to falter, replaced by a glimpse of reluctant respect for the gravity of what lay in their hands. Jordan looked up, and for a fleeting heartbeat, their eyes locked with Taylor\'s, a wordless clash of wills softening into an uneasy truce.\n\nIt was a small transformation, barely perceptible, but one that Alex noted with an inward nod. They had all been brought here by different paths\n################\nOutput:\n("entity"<|>"Alex"<|>"person"<|>"Alex is a character who experiences frustration and is observant of the dynamics among other characters.")##\n("entity"<|>"Taylor"<|>"person"<|>"Taylor is portrayed with authoritarian certainty and shows a moment of reverence towards a device, indicating a change in perspective.")##\n("entity"<|>"Jordan"<|>"person"<|>"Jordan shares a commitment to discovery and has a significant interaction with Taylor regarding a device.")##\n("entity"<|>"Cruz"<|>"person"<|>"Cruz is associated with a vision of control and order, influencing the dynamics among other characters.")##\n("entity"<|>"The Device"<|>"technology"<|>"The Device is central to the story, with potential game-changing implications, and is revered by Taylor.")##\n("relationship"<|>"Alex"<|>"Taylor"<|>"Alex is affected by Taylor\'s authoritarian certainty and observes changes in Taylor\'s attitude towards the device."<|>"power dynamics, perspective shift"<|>7)##\n("relationship"<|>"Alex"<|>"Jordan"<|>"Alex and Jordan share a commitment to discovery, which contrasts with Cruz\'s vision."<|>"shared goals, rebellion"<|>6)##\n("relationship"<|>"Taylor"<|>"Jordan"<|>"Taylor and Jordan interact directly regarding the device, leading to a moment of mutual respect and an uneasy truce."<|>"conflict resolution, mutual respect"<|>8)##\n("relationship"<|>"Jordan"<|>"Cruz"<|>"Jordan\'s commitment to discovery is in rebellion against Cruz\'s vision of control and order."<|>"ideological conflict, rebellion"<|>5)##\n("relationship"<|>"Taylor"<|>"The Device"<|>"Taylor shows reverence towards the device, indicating its importance and potential impact."<|>"reverence, technological significance"<|>9)##\n("content_keywords"<|>"power dynamics, ideological conflict, discovery, rebellion")<|COMPLETE|>\n#############################\nExample 2:\n\nEntity_types: [person, technology, mission, organization, location]\nText:\nThey were no longer mere operatives; they had become guardians of a threshold, keepers of a message from a realm beyond stars and stripes. This elevation in their mission could not be shackled by regulations and established protocols—it demanded a new perspective, a new resolve.\n\nTension threaded through the dialogue of beeps and static as communications with Washington buzzed in the background. The team stood, a portentous air enveloping them. It was clear that the decisions they made in the ensuing hours could redefine humanity\'s place in the cosmos or condemn them to ignorance and potential peril.\n\nTheir connection to the stars solidified, the group moved to address the crystallizing warning, shifting from passive recipients to active participants. Mercer\'s latter instincts gained precedence— the team\'s mandate had evolved, no longer solely to observe and report but to interact and prepare. A metamorphosis had begun, and Operation: Dulce hummed with the newfound frequency of their daring, a tone set not by the earthly\n#############\nOutput:\n("entity"<|>"Washington"<|>"location"<|>"Washington is a location where communications are being received, indicating its importance in the decision-making process.")##\n("entity"<|>"Operation: Dulce"<|>"mission"<|>"Operation: Dulce is described as a mission that has evolved to interact and prepare, indicating a significant shift in objectives and activities.")##\n("entity"<|>"The team"<|>"organization"<|>"The team is portrayed as a group of individuals who have transitioned from passive observers to active participants in a mission, showing a dynamic change in their role.")##\n("relationship"<|>"The team"<|>"Washington"<|>"The team receives communications from Washington, which influences their decision-making process."<|>"decision-making, external influence"<|>7)##\n("relationship"<|>"The team"<|>"Operation: Dulce"<|>"The team is directly involved in Operation: Dulce, executing its evolved objectives and activities."<|>"mission evolution, active participation"<|>9)<|COMPLETE|>\n("content_keywords"<|>"mission evolution, decision-making, active participation, cosmic significance")<|COMPLETE|>\n#############################\n\n#############################\n-Real Data-\n######################\nEntity_types: organization,person,geo,event,category\nText: AFP考试介绍，难度怎么样？AFP，即金融理财师，是国际金融领域值得认可的、含金量较高的资格认证，对于国内考生来说，报考AFP前需要了解什么?考试难度怎么样?一、AFP是什么?AFP资格认证是一项国际标准，内容本土化，水平国际化。2009年以前，AFP资格证书由中国金融教育发展基金会金融理财标准委员会(标委会)进行认证，2009年开始，随着标委会转型为国际金融理财标准委员会中国专家委员会和现代国际金融理财标准(上海)有限公司(也即FPSB China)之后，AFP金融理财师由FPSB China进行认证。AFP已经纳入FPSB国际认证体系。\n######################\n'}, {'role': 'user', 'content': 'Output:'}]
It's fixed.
Pull the latest code.
Or, upgrade to nightly version of docker image.
use the nightly version , it starts ,but at the end ,error:AttributeError: 'CommunityReportsExtractor' object has no attribute '_on_error'