different-ai/file-organizer-2000

Bug: Missing publishableKey.

Closed this issue · 7 comments

Martin-Milbradt commented

I'm getting the error on the self-hosted version. What could be wrong?

ENABLE_USER_MANAGEMENT False
   NEXT_PUBLIC_CLERK_IS_SATELLITE='true'`,n9="x-middleware-override-headers",n5="x-middleware-request",n8=(e,t,r)=>
   [...]
Error: @clerk/nextjs: Missing publishableKey. You can get your key at https://dashboard.clerk.com/last-active?path=api-keys.

File Organizer API Key is set.
OPENAI_API_KEY set in environment variables and working.
Version: 1.4.4 (Server and plugin).
HTTP Status: 500

Note: I deleted .eslintrc since it caused issues and I think it's just linter settings.
It used to work a few versions ago.

Startup:

npm i
npm run build
$env:ENABLE_USER_MANAGEMENT=$false
npm run start
ashgansh commented

hi @Martin-Milbradt how are you running the api at the moment?

ashgansh commented

on my machine i run it like this:

npm run build
OPENAI_API_KEY=[some key] npm run start
Martin-Milbradt commented

I've set the OPENAI_API_KEY in the environment variables, and it used to work a few versions of file-organizer ago.

Martin-Milbradt commented

Still doesn't work after rebuild and specifying ENABLE_USER_MANAGEMENT=$false, but it's getting more complicated.

Output:

ENABLE_USER_MANAGEMENT False
   NEXT_PUBLIC_CLERK_IS_SATELLITE='true'`,n9="x-middleware-override-headers",n5="x-middleware-request",n8=(e,t,r)=>
   [...]
Error: @clerk/nextjs: Missing publishableKey. You can get your key at https://dashboard.clerk.com/last-active?path=api-keys.
ashgansh commented

hmmm damn that sucks sorry about that

i just pushed a commit that i believe should fix it, could you pull and try again?

Martin-Milbradt commented

Looking good! There is an error message displayed, but the file is successfully moved.
Note: I'd expect the Tag written to get added, but fileorganizer doesn't catch that.
Note2: I'd expect it to go to Media/Written- all other articles by Asterisks are there. Is fileorganizer supposed to log the "reasoning" for its actions (my logs are empty, see #47).
image

ashgansh commented

hi @Martin-Milbradt we're getting significantly more issues since we downgraded to gpt-3.5-turbo :( with these types of things

there's also a few underlying problem (and we could do better error management and recover etc.) but simply upgrading to gpt-4-turbo solves 60% of issues on our side.

we will push a new update today to give more control over this