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

[BUG] Scraper not scrapping data? #92

Closed
aivct opened this issue Dec 30, 2022 · 5 comments
Closed

[BUG] Scraper not scrapping data? #92

aivct opened this issue Dec 30, 2022 · 5 comments
Labels
bug Something isn't working ⚠️ high-priority ⚠️

Comments

@aivct
Copy link

aivct commented Dec 30, 2022

Behaviour:
image
Expected Behaviour:
image
Steps to Reproduce:
No idea.
These bugs are most prevalent when there is an error on the main chat page itself, but that's just anecdotal for now.
Wait a long time (ie, go take a nap) and see what happens in the morning, because that usually causes weirdness.

Notes
For some reason, the scraper has kind of bugged out. I regret not saving any logs initially, but I just noticed it. The following are logs from when I opened it again. And now, it is still refusing to save the old logs.

image

There are probably at least two bugs here.

  1. Scarper isn't properly saving new chats.
  2. Scraper is being weird with recognizing and saving over old chats.

PS: Oh, and whitespace for humans are still wrong. Tabs and indents are not displayed correctly, ugh.

@aivct
Copy link
Author

aivct commented Dec 30, 2022

This may or may not be related. OpenAI has also triggered its own error at the same time.

image

@benf2004 benf2004 added the bug Something isn't working label Dec 31, 2022
@benf2004
Copy link
Member

Something strange is going on right now. It's not working for me.

@aivct
Copy link
Author

aivct commented Jan 13, 2023

@benf2004 are you saying you can't reproduce the bug or that you are also reproducing the bug?

@benf2004
Copy link
Member

The scraper is not really working for me right now.

@aivct
Copy link
Author

aivct commented Jan 16, 2023

I think I see one source of the issue.

The ID is unified, but the thread doesn't know that, so it does weird things like this:

image

If you look in the last index of t[], it'll give you the thread... with the wrong id, and the unified id is nowhere to be found.

Last time I checked, array[null] is invalid (actually any invalid values seem to just be ignored, gotta love JS failing silently)

Anyways, checking that the index isn't null and inserting it afterwards is a duct tape fix that I'll try. Better to save twice than to overwrite.

This STILL might not fix every cause, but let's just re-open the issue or get a new one in that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ⚠️ high-priority ⚠️
Projects
None yet
Development

No branches or pull requests

2 participants