fix: 🐛 Codebase indexing is not starting on load #5993
Conversation
|
Your cubic subscription is currently inactive. Please reactivate your subscription to receive AI reviews and use cubic. |
✅ Deploy Preview for continuedev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
dosubot
bot
added
the
size:XS
|
@chezsmithy how does switching the |
chezsmithy
changed the title
|
Fix to resolve inital loading issues caused by: #5894 |
|
#5994 - this will fix the prettier issue. |
Well now, only the async gods will know. I fixed it using code inspection to to the previous state, but upon further review, there is a crazy amount of aysnc functions being orchestrated in CodeBaseIndexer.ts. My best guess is by adding the await (added to fix an eslint issue), it's not letting the outer async function to continue which is blocking the indexing start. |
@Patrick-Erichsen ironically caused by my PR :) Thank you. PS, I have prettier enabled fully so this shouldn't happen again. |
|
No worries, took us way to long to get prettier enabled in CI! But yeah that seems plausible, works for me so 🤷♂️ Linting fix PR has been merged so just merge |
chezsmithy
force-pushed
the
fix-codebase-indexing-not-starting
branch
from
66a4c90 to
e391d58
Compare
Description
Codebase indexing was not starting on load of the extension.
Checklist
Screenshots
[ For visual changes, include screenshots. Screen recordings are particularly helpful, and appreciated! ]
Tests
Tested through visual inspection of loading the extension in the debugger and observing indexing now seems to start as expected.