-
Notifications
You must be signed in to change notification settings - Fork 0
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
Try on kisski #84
base: main
Are you sure you want to change the base?
Try on kisski #84
Conversation
need hf token
Waiting for HF_token authorization
…me testing. From Docker's log it looks like it is running on the CPU and needs some testing.
currently got "Error during response generation: Input length of input_ids is 200, but `max_length` is set to 200. This can lead to unexpected behavior."
The chat works after the update but is still on the CPU, making it slow. I'll try utilizing the laptop's NVIDIA RTX 500 Ada Generation GPU to improve performance.
Still need time for the Kisski API key
Miss spell "openai.chat.completions.create" to "openai.ChatCompletion.create"
Now as they told me: |
.env
Outdated
@@ -1 +1 @@ | |||
# HF_TOKEN=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 | |||
KISSKI_API_KEY='b6c89c0b03ba5bd30170933cc6861886' |
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.
Hi Yixin,
never store API keys on Github so that others can read them.
I recommed you to revoke the huggingface and the Kisski key. Otherwise others can use the platforms on your behalf.
Best,
Robert
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.
Hi Robert,
Thanks for your advice. I got a message last night, and in my latest version that I replaced it as "KISSKI_API_KEY=your_api_key" and uploaded it yesterday, but I don't know why you can still read it.
Best,
Yixin
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.
Because the git history contains it. Again, I recommend to revoke all keys you put on the internet.
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.
Do you know how to delete them? I tried using the "delete file" function, but it does not seem to work.
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.
I mean to delete the history
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.
You should revoke the key instead of deleting the history.
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.
E.g. as shown here: https://huggingface.co/docs/hub/en/security-tokens#how-to-manage-user-access-tokens or by sending an email to the KISSKI folks
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.
Ahh, ok thank you, I will write an email to them to recreate a new one , thank you again
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.
They have already created a new one and the HF token has already been deleted.
This Version base on the Kisski, but still need time for the Kisski API key