Open Branchenprimus opened 2 weeks ago
Hi @Branchenprimus!
NEXTAUTH_SECRET
is in the NextAuth docs but I don't really see the need for it atm. It could be removed if you want to open a PR or I can otherwise. Update: I think I lied :) Here is the error I get without it so it might be used for the JWT, but I think it is arbitrary what key is used. Here is the error I got without it:
[next-auth][warn][NO_SECRET]
https://next-auth.js.org/warnings#no_secret
[next-auth][error][JWT_SESSION_ERROR]
https://next-auth.js.org/errors#jwt_session_error decryption operation failed {
message: 'decryption operation failed',
stack: 'JWEDecryptionFailed: decryption operation failed\n' +
OAUTH_GITHUB_ID/OAUTH_GITHUB_SECRET
are kicked back when you create an OAuth. You could setup your own for example. Here is a screen cap of one that would work if you were running on your local machine. The key item is the callback URL needs to match your URL of the service. So http://localhost:3000/api/auth/callback/github
would work for starting the service with npm run dev
and going to http://localhost:3000
.
For IL_GRANITE_API
and IL_MERLINITE_MODEL_NAME
those are locked down in a security group since they are running non-quantized version of the models on A100s so they are not exposed to the Internets at the moment. What you can do in the meantime is create your own custom endpoint that could be instructlab running on your machine or anywhere and hit a quantized version.
If you want to hit me up on Slack and you're looking to dev don't hesitate and we can figure out access to the non-quant. Also the community UI meeting is tomorrow at 1pm EST if you feel like popping in! Link to calendar
Cheers!
Hi team,
Thank you for developing the InstructLab UI! I'm excited to start using it, but I'm currently having trouble getting it up and running. The main issue seems to be understanding and setting the
.env
variables.Here's what I have in my
.env
file:NEXTAUTH_SECRET
.Any guidance would be greatly appreciated!
Thanks, Jan