Add IndexingQueue to handle indexing tasks sequentially #1593
Conversation
* fix(extensions): schema for db ctx provider * fix: invalid enum
* 👷 CI for jetbrains * default working dir * changelog * build binaries * binary testing setup * idesettings * core binary testing * run binary tests in ci * remove unused targets * needs build * console.log bin contents * fix ci * fix win32 binary download * test * no linux arm64 * macos latest * macos-12 * binary permissions * upload logs * fix * upload full folder as binary artifact * test * test macos only * set full execute permissions * copy sqlite binary * cd * it worked! * build again in test job * debug * remove timeout * info * log * log2 * more logs * catch * fewer logs * test all platforms * test downloaded artifact * needs build * updates * build * false * release * add tag and upload binaryes * change tag name * proper artifact upload * jest updates * ✅ generate a few unit tests with Continue * fix imports related to IdeSettings * run tsc on PRs * remove shareSession command (unused) * update release process * update plugin version * don't show ghost text when jetbrains completion visible * run jetbrains ci in main
* ✨ use and cache imports for autocomplete * fix tsc
* feat: toast notification for config updates * feat: only trigger toast on config.json save
* feat: open pane on activation * comment out testing code
* doc: prompt file typo + clarifications * fix: add back correct docs
* chore(gui): remove unused pages * feat: add embeddings step * feat: update styles * feat: copy button updates * fix: correct pull command for embed model * fix: remove commented code * fix: remove commented code * feat: simplify copy btn props * chore: rename onboarding selection event * feat: add provider config * fix: undo msg name * remove dead code * fix: invalid mode check
…uedev#1584) - Introduce reranker concept - List available reranker options - Provide configuration instructions - Update keywords to include "reranker"
- Added NPM script method - Added VS Code task method - Update contributing guidelines
- Change PR target to `dev` branch - Update `CONTRIBUTING.md` instructions
…ontinuedev#1579) - Moved examples to configuration.md - Deleted the separate examples.md file - Updated sidebar order and links - Improved readability and structure in configuration.md
- Introduce IndexingQueue class - Update core.ts to use IndexingQueue - Enhance IndexingProgressBar UI - Update IndexingProgressUpdate interface
|
I think we're going to want to do something slightly different here. The biggest concern for me is that the docs indexing won't happen until main indexing has completed, which might force the user to wait some time. The alternative that I think would be ideal is to keep a "stack" of currently running jobs. They would all run in parallel, but all updates would be attached to a certain "job id" and the last created job id would always be the one displayed in the loading bar, until it was done, at which point the job beneath it, if still progressing, would take over. On hover, it could display the full stack of current jobs. I think this would require a) updating the IndexingProgressUpdate type to include a "jobId", b) setting that "jobId" to a random UUID at the beginning of any job and making sure that the same ID is used throughout the job, c) writing the basic "stack" logic in the IndexingProgressBar component I'm going to close this, but the thought process here was really valuable, so thank you for making the draft |
Description
Checklist
dev, rather thanmain