Streamlining and Organizing our Issue Tracker

[vvatanabe]

Hey @sashabaranov, thanks for running this awesome repository. I really value this open-source project and I've got a few suggestions that could help us continue its success.

I've noticed a few duplicate and unresolved (though actually resolved) issues popping up on the go-openai Issue Tracker. While they might seem like small things individually, when they start piling up, they could potentially hinder our progress with maintenance.

To tackle this problem, here are a few actions I propose:

• Let's consolidate duplicate issues to focus all conversations and solutions on a single thread.
• Once an issue has been resolved, let's close it properly to keep a clear view of the current issues.
• I suggest we add appropriate labels to our issues.

Unless there are any objections, I'm happy to get started on these tasks.

---

TODO:

• consolidate duplicate issues to focus all conversations and solutions on a single thread.
• Once an issue has been resolved, and close it properly to keep a clear view of the current issues.
• add appropriate labels to our issues.
• set up closing-inactive-issues in GitHub Action

[vvatanabe]

@sashabaranov I'll start implementing the proposed actions gradually. Please let me know if you have any concerns.

[vvatanabe]

I've finished labeling the open issues.

Refs: https://github.com/sashabaranov/go-openai/labels

[vvatanabe]

I've closed the following issue as it has already been completed.

• Can AudioRequest support byte array as parameter in the future?
• Missing error processing for Audio
• Azure OpenAI list models
• Not as expected err: unexpected end of JSON input
• whisper openai.AudioRequest.FilePath
• Support multiple prompts in CompletionRequest
• Add a Mocked Server for Testing
• Demo code not working
• how to download fine-turns files
• The authToken cannot be passed in when setting the http proxy
• when the apikey is use out money it return EOF?
• APIError is suggested to be returned from stream.Recv()
• Add option to choose language in whisper API
• Implement June OpenAI updates
• error, unexpected end of JSON input
• usage for stream output in chat completion
• EOF
• Upgrade error reporting for streams
• Completion request error for LogitBias

[vvatanabe]

I closed due to duplication with #9 on the Temperature issue.

• Model hyperparams with Temperature value 0 is not being respected
• Temperature param being ignored?
• How to achieve that in the same session, the results of two identical request parameters cannot be the same
• Inconsistent results from GPT with temperature = 0

[vvatanabe]

I've closed this due to lack of comments over an extended period, even though a solution has been proposed.

• error on Cloud Run
• How to close the flow when using the following code?
• Terminates a "stream for" loop
• Allow headers in the proxy
• [ERR] invalid character '<' looking for beginning of value
• 费流量
• CreateChatCompletionStream接口stream返回时，并不是真的流式返回，日志显示都是在同一秒
• 请问请求体中的role字段有什么实际用途
• Expose APIError required
• v1.9.1 check sum mismatched in sum.golang.org
• 通过代理调用 报错： malformed HTTP response
• "https://api.openai.com/v1/chat/completions": x509: certificate
• syntax error: unexpected |, expecting semicolon or newline or }
• unexpected [, expecting semicolon or newline or }

[vvatanabe]

I closed due to duplication with #62 on the tokenizer issue.

• Add a method to query the remaining tokens of key
• Ability to count tokens before sending
• 如何获取 花费的 token 数？

[sashabaranov]

@vvatanabe thank you so much, this is monumental work! What do you think about auto-closing stale issues? https://docs.github.com/en/github-ae@latest/actions/managing-issues-and-pull-requests/closing-inactive-issues

[vvatanabe]

@sashabaranov This is exactly what we've been looking for!

For example, you can comment if an issue has been inactive for 30 days to prompt participants to take action. Then, if no additional activity occurs after 14 days, you can close the issue.

[vvatanabe]

@sashabaranov
On another note, upon triaging our issues, I've found that there's a considerable amount of 'questions'.
Shouldn't we discourage posting 'questions' as 'issues'? What about directing them towards 'discussions' or 'Stack Overflow'? This seems to be the approach adopted by many prominent open-source software projects.

[vvatanabe]

DONE