-
Notifications
You must be signed in to change notification settings - Fork 359
introduce chat api to the project supported by langchain's sql-agent #2788
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
base: main
Are you sure you want to change the base?
Conversation
* remove project service to drop support for legacy version of subql node
"lodash": "^4.17.21", | ||
"pg": "^8.12.0", | ||
"pg-tsquery": "^8.4.2", | ||
"postgraphile": "^4.13.0", | ||
"postgraphile-plugin-connection-filter": "^2.2.2", | ||
"rxjs": "^7.1.0", | ||
"typeorm": "^0.3.23", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does langchain require typeorm? Could we use sequelize here for consistency?
@@ -85,6 +86,17 @@ export class ConfigureModule { | |||
pgClient._explainResults = []; | |||
}); | |||
} | |||
// todo: support ssl | |||
const dataSource = new DataSource({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we specify this as read only?
choices: [ | ||
{ | ||
index: 0, | ||
message: {role: 'assistant', content: fullResponse}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the right behaviour to send the full response again at the end of a stream?
Description
integrate llm chat api to query data from database
other minor changes
Fixes # (issue)
Type of change
Please delete options that are not relevant.
Checklist