Closed kleenkanteen closed 1 year ago
Hey @kleenkanteen thanks for reporting. Just tried a clean install on my end and not able to reproduce the issue. Would you mind sharing:
Also just confirming:
You have the latest dependencies installed:
rm -r node_modules
npm install
main
branchThanks!
Just did a fresh install. Followed the steps to deploy the functions and push migrations to my db. Can sign up without errors now. Odd. Am on W10, Brave browser, latest versions for both. Node 20.10. On main branch.
Strange! Glad it's working now though 👍
Just did a fresh install. Followed the steps to deploy the functions and push migrations to my db. Can sign up without errors now. Odd. Am on W10, Brave browser, latest versions for both. Node 20.10. On main branch.
Hi, I'm having the same issue - could you detail exactly what you did to address it? Did you reinstall node? I reinstalled supabase and cloned the repo from scratch too, but I'm still getting the same error
@gregnr could we reopen the issue?
Didn't reinstall node. Did a fresh clone. Try reinstalling node if that doesn't work.
On Fri., Mar. 15, 2024, 3:22 a.m. iwo9, @.***> wrote:
Hi, I'm having the same issue - could you detail exactly what you did to address it? Did you reinstall node?
— Reply to this email directly, view it on GitHub https://github.com/supabase-community/chatgpt-your-files/issues/8#issuecomment-1999075248, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQF3ZKURS653CC7WRHXME4DYYKORTAVCNFSM6AAAAAA72OTQPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJZGA3TKMRUHA . You are receiving this because you modified the open/close state.Message ID: @.***>
That's so weird. I've reinstalled node, supabase, and done a fresh clone multiple times each but keep getting the same issue
Try cleaning your npm cache. And if that doesn't work, downgrading the nextjs version.
I recommend not following this repo btw because the chunking and retrieval is very poor without a LLM framework. I tried it on a 1000 word file and it retrieved way too much. Filled up the max tokens I could pass into gpt 3.5. Try using haystack instead for chunking and retrieval. I did a bunch of research and it's better designed than langchain and llamaindex.
On Sat., Mar. 16, 2024, 1:00 a.m. iwo9, @.***> wrote:
That's so weird. I've reinstalled node, supabase, and done a fresh clone multiple times each but keep getting the same issue
— Reply to this email directly, view it on GitHub https://github.com/supabase-community/chatgpt-your-files/issues/8#issuecomment-2001671803, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQF3ZKQVX526UW5MMXMJCHTYYPGXNAVCNFSM6AAAAAA72OTQPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBRGY3TCOBQGM . You are receiving this because you modified the open/close state.Message ID: @.***>
K thanks, I'll look into that. Any recommendations for using Mistral 7B instead of GPT? I've seen a bit of work on RAG with Mistral, but mostly just for generation, nothing covering metadata extraction etc.
Based on what I've seen, results from it aren't the best. The model can be switched out easily so you can test with different ones for best results.
On Sat., Mar. 16, 2024, 2:29 a.m. iwo9, @.***> wrote:
K thanks, I'll look into that. Any recommendations for using Mistral 7B instead of GPT? I've seen a bit of work on RAG with Mistral, but mostly just for generation, nothing covering metadata extraction etc.
— Reply to this email directly, view it on GitHub https://github.com/supabase-community/chatgpt-your-files/issues/8#issuecomment-2001845762, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQF3ZKTNUQMQD6TQ3T3MLWTYYPRFDAVCNFSM6AAAAAA72OTQPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBRHA2DKNZWGI . You are receiving this because you modified the open/close state.Message ID: @.***>
Bug report
Describe the bug
When I run npm run dev, open localohst:3000, and try to sign up, after clicking sign up it gives me the error "Error: Hydration failed because the initial UI does not match what was rendered on the server." That was with the default starter.