Skip to content
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

Not working #3

Open
idrisalliance opened this issue May 8, 2023 · 13 comments
Open

Not working #3

idrisalliance opened this issue May 8, 2023 · 13 comments

Comments

@idrisalliance
Copy link

we tried to implement this code... it is not working

@draeder
Copy link

draeder commented May 25, 2023

It works fine for me.

  1. Clone the repo
  2. npm install inside the repo folder
  3. npm run dev
  4. In your browser: http://localhost:3000

@IdrisGame
Copy link

yeah it does not work it gives error at the end

@draeder
Copy link

draeder commented Jun 1, 2023

@IdrisGame What is the error?

@IdrisGame
Copy link

@IdrisGame What is the error?

Try it, once I put the api, then do the search it gives Answer Error. Doesnt output the answer but gives Answer error

@draeder
Copy link

draeder commented Jun 1, 2023

These are the possible errors: https://github.com/search?q=repo%3Amckaywrigley%2Fclarity-ai%20answer%20error&type=code

What is the exact error in your browser console logs?

@IdrisGame
Copy link

These are the possible errors: https://github.com/search?q=repo%3Amckaywrigley%2Fclarity-ai%20answer%20error&type=code

What is the exact error in your browser console logs?

Have you tried on your end do you get any error. Also I dont know if is because I put gpt 3 instead of gpt3.5

@draeder
Copy link

draeder commented Jun 1, 2023

Coincidentally, I did get errors this time. Interestingly it seems to be that specific questions cause errors. I asked it, "What is cool?".

The error it threw in the browser:

1 of 1 unhandled error

Unhandled Runtime Error
Error: Internal Server Error

Source
components/Search.tsx (42:12) @ fetchSources

  40 | if (!response.ok) {
  41 |   setLoading(false);
> 42 |   throw new Error(response.statusText);
     |        ^
  43 | }
  44 | 
  45 | const { sources }: { sources: Source[] } = await response.json();
Call Stack
async handleSearch
components/Search.tsx (27:20)

The error it threw on the server:

[DOMException [InvalidCharacterError]: "[class]" did not match the Name production]

@IdrisGame
Copy link

Are you able to fix it?

@JenniferDevelopez
Copy link

I have the same error "Unhandled Runtime Error"

@jpotw
Copy link

jpotw commented Feb 4, 2024

Coincidentally, I did get errors this time. Interestingly it seems to be that specific questions cause errors. I asked it, "What is cool?".

The error it threw in the browser:

1 of 1 unhandled error

Unhandled Runtime Error
Error: Internal Server Error

Source
components/Search.tsx (42:12) @ fetchSources

  40 | if (!response.ok) {
  41 |   setLoading(false);
> 42 |   throw new Error(response.statusText);
     |        ^
  43 | }
  44 | 
  45 | const { sources }: { sources: Source[] } = await response.json();
Call Stack
async handleSearch
components/Search.tsx (27:20)

The error it threw on the server:

[DOMException [InvalidCharacterError]: "[class]" did not match the Name production]

ran it and getting the same Error message.

@Yevanchen
Copy link

hey guys the error message indicates that an invalid URL was passed to the URL constructor in your Next.js API route at pages/api/sources.ts on line 38.
There are two main modifications:

  1. When extracting links, the cleanedHref is decoded and checked to ensure that the decoded link starts with "http://" or "https://" to ensure it is a valid absolute URL.
  2. When filtering links, the code for creating a URL object is wrapped in a try-catch block. If an error is thrown due to an invalid URL, we catch the error, log it, and return false to exclude the link from the filtered results.
    With these modifications, invalid URLs should be handled properly and prevent the occurrence of TypeError: Invalid URL errors.

@turnerll
Copy link

turnerll commented Apr 3, 2024

What's the solution? I have the same problem here.
https://share.zight.com/o0uOnW4L

@ziliangpeng
Copy link

+1. Can't get it to work. The project also seems unmaintained?

I'm working on a new one, with local LLM support. The landscape is already so different than when this project started.

sliss referenced this issue in vkarpov15/clarity-ai Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants