Bug: repository chatbot tracker issue

[a0m0rajab]

Describe the bug

• The repository chatbot is not working,
• when we get an unindexed repo it will be loading forever, we need to handle that
• for the conversation, we are getting two errors:

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'substring')
    at c (github.ts.3aad7e0a.js:96:117)
    at d (github.ts.3aad7e0a.js:96:1045)
    at async onClick (github.ts.3aad7e0a.js:96:2910)

Related page:

ai/src/repo-query/pages/chat.tsx

Line 210 in bc44a66

id="question-suggestion"

Some errors are not printing the message:
like this one:

ai/src/repo-query/pages/chat.tsx

Line 29 in bc44a66

console.error(dataLine);

this needs a minor refactor

Steps to reproduce

1. go to https://github.com/open-sauced/ai
2. try to use the chatbot
3. Tada!

Browsers

No response

Additional context (Is this in dev or production?)

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Contributing Docs

• I agree to follow this project's Contribution Docs

[a0m0rajab]

This is happening due to the data chunk that we are getting from the API endpoint, I think we need to check the endpoint too.

Related endpoint and query:

fetch("https://opensauced.tools/query", {
  "headers": {
    "accept": "*/*",
    "accept-language": "en,tr-TR;q=0.9,tr;q=0.8,en-US;q=0.7,ar;q=0.6,it;q=0.5",
    "content-type": "application/json",
    "sec-ch-ua": "\"Google Chrome\";v=\"119\", \"Chromium\";v=\"119\", \"Not?A_Brand\";v=\"24\"",
    "sec-ch-ua-mobile": "?0",
    "sec-ch-ua-platform": "\"Windows\"",
    "sec-fetch-dest": "empty",
    "sec-fetch-mode": "cors",
    "sec-fetch-site": "cross-site"
  },
  "referrer": "https://github.com/open-sauced/ai",
  "referrerPolicy": "no-referrer-when-downgrade",
  "body": "{\"query\":\"How do I run this locally?\",\"repository\":{\"owner\":\"open-sauced\",\"name\":\"ai\",\"branch\":\"HEAD\"}}",
  "method": "POST",
  "mode": "cors",
  "credentials": "omit"
});

[github-actions]

🎉 This issue has been resolved in version 1.14.3-beta.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 1.15.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀