bugfix: jumps over deleted messages in history when calling api #350
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(cherry picked from commit 7a0f3f3)
|
Someone is attempting to deploy a commit to a Personal Account owned by @Kerwin1202 on Vercel. @Kerwin1202 first needs to authorize it. |
(cherry picked from commit f5ff675)
zhujunsan
changed the title
zhujunsan
changed the title
(cherry picked from commit 9823402)
Kerwin1202
reviewed
Oct 20, 2023
service/src/chatgpt/index.ts
Outdated
| import httpsProxyAgent from 'https-proxy-agent' | ||
| import fetch from 'node-fetch' | ||
| import type { AuditConfig, CHATMODEL, KeyConfig, UserInfo } from 'src/storage/model' | ||
| import { Status } from "src/storage/model"; |
Member
There was a problem hiding this comment.
import { Status } from '../storage/model'
麻烦改为这样呢，一个是都单引号，统一一下，否则校验感觉过不去， 另一个 我跑你这样会报错，../ 就不会
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
fix #349