-
Notifications
You must be signed in to change notification settings - Fork 8.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
企微群里多人会话并发支持 #456
Labels
💪 enhancement
New feature or request
Comments
you can create conversations by using different user ids. |
使用场景是机器人参与广场里的讨论, 所以上下文是针对整个群而非每个用户。 虽然可以通过队列来解决。 conversation_id每次回答都会生成一个新的, 旧的就 404. 我感觉不太合理。 conversation_id 应该可以一直保留着 |
The conversation_id will be kept after the first conversation as long as the user_id remains the same. |
laipz8200
added a commit
that referenced
this issue
Nov 14, 2024
Refactored LLM node tests to enhance clarity and maintainability by creating test scenarios for different file input combinations. This restructuring replaces repetitive code with a more concise approach, improving test coverage and readability. No functional code changes were made. References: #123, #456
laipz8200
added a commit
that referenced
this issue
Nov 14, 2024
Ensure that messages are only created from non-empty text segments, preventing potential issues with empty content. test: add scenario for file variable handling Introduce a test case for scenarios involving prompt templates with file variables, particularly images, to improve reliability and test coverage. Updated `LLMNodeTestScenario` to use `Sequence` and `Mapping` for more flexible configurations. Closes #123, relates to #456.
laipz8200
added a commit
that referenced
this issue
Nov 14, 2024
Refactored LLM node tests to enhance clarity and maintainability by creating test scenarios for different file input combinations. This restructuring replaces repetitive code with a more concise approach, improving test coverage and readability. No functional code changes were made. References: #123, #456
laipz8200
added a commit
that referenced
this issue
Nov 14, 2024
Ensure that messages are only created from non-empty text segments, preventing potential issues with empty content. test: add scenario for file variable handling Introduce a test case for scenarios involving prompt templates with file variables, particularly images, to improve reliability and test coverage. Updated `LLMNodeTestScenario` to use `Sequence` and `Mapping` for more flexible configurations. Closes #123, relates to #456.
laipz8200
added a commit
that referenced
this issue
Nov 15, 2024
Refactored LLM node tests to enhance clarity and maintainability by creating test scenarios for different file input combinations. This restructuring replaces repetitive code with a more concise approach, improving test coverage and readability. No functional code changes were made. References: #123, #456
laipz8200
added a commit
that referenced
this issue
Nov 15, 2024
Ensure that messages are only created from non-empty text segments, preventing potential issues with empty content. test: add scenario for file variable handling Introduce a test case for scenarios involving prompt templates with file variables, particularly images, to improve reliability and test coverage. Updated `LLMNodeTestScenario` to use `Sequence` and `Mapping` for more flexible configurations. Closes #123, relates to #456.
laipz8200
added a commit
that referenced
this issue
Nov 18, 2024
Refactored LLM node tests to enhance clarity and maintainability by creating test scenarios for different file input combinations. This restructuring replaces repetitive code with a more concise approach, improving test coverage and readability. No functional code changes were made. References: #123, #456
laipz8200
added a commit
that referenced
this issue
Nov 18, 2024
Ensure that messages are only created from non-empty text segments, preventing potential issues with empty content. test: add scenario for file variable handling Introduce a test case for scenarios involving prompt templates with file variables, particularly images, to improve reliability and test coverage. Updated `LLMNodeTestScenario` to use `Sequence` and `Mapping` for more flexible configurations. Closes #123, relates to #456.
laipz8200
added a commit
that referenced
this issue
Nov 18, 2024
Refactored LLM node tests to enhance clarity and maintainability by creating test scenarios for different file input combinations. This restructuring replaces repetitive code with a more concise approach, improving test coverage and readability. No functional code changes were made. References: #123, #456
laipz8200
added a commit
that referenced
this issue
Nov 18, 2024
Ensure that messages are only created from non-empty text segments, preventing potential issues with empty content. test: add scenario for file variable handling Introduce a test case for scenarios involving prompt templates with file variables, particularly images, to improve reliability and test coverage. Updated `LLMNodeTestScenario` to use `Sequence` and `Mapping` for more flexible configurations. Closes #123, relates to #456.
laipz8200
added a commit
that referenced
this issue
Nov 22, 2024
Refactored LLM node tests to enhance clarity and maintainability by creating test scenarios for different file input combinations. This restructuring replaces repetitive code with a more concise approach, improving test coverage and readability. No functional code changes were made. References: #123, #456
laipz8200
added a commit
that referenced
this issue
Nov 22, 2024
Ensure that messages are only created from non-empty text segments, preventing potential issues with empty content. test: add scenario for file variable handling Introduce a test case for scenarios involving prompt templates with file variables, particularly images, to improve reliability and test coverage. Updated `LLMNodeTestScenario` to use `Sequence` and `Mapping` for more flexible configurations. Closes #123, relates to #456.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
现在接入机器人时候发现群里聊天会有并发问题:
conversation_id 如果使用了一次, 下一个人传入相同的conversation_id会提示 404.
是否可以支持保留 conversation_id 可用状态。
The text was updated successfully, but these errors were encountered: