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

[wip] choredb #506

Draft
wants to merge 33 commits into
base: self_configure
Choose a base branch
from
Draft

[wip] choredb #506

wants to merge 33 commits into from

Conversation

JegernOUTT
Copy link
Member

No description provided.

Add functionality to track ongoing work in VecDb through a new `OngoingWork` structure stored in a `HashMap`. Introduce methods `ongoing_update_or_create` and `ongoing_dump` in `vdb_highlev.rs` to manage this data. Incorporate mutexes for thread safety and use `IndexMap` for ordered storage. In `handlers_memdb.rs`, create corresponding API endpoints `handle_ongoing_update_or_create` and `handle_ongoing_dump` to update ongoing work status and retrieve the summary, respectively. Ensure API responses are properly formatted in JSON or plain text.
@JegernOUTT JegernOUTT marked this pull request as draft December 18, 2024 03:29
- Update tool subset handling in subchat functions to use `Option<Vec<String>>`.
- Change vector initializations from `vec![]` to `Some(vec![])` where applicable.
- Modify database schema to include new fields `cthread_max_new_tokens` and `cthread_n` with default values.
- Use `PathBuf` for database path configuration in `_make_connection`.
- Initialize `config_dir` with a clone to ensure proper usage context.
- Enhance database thread structure with default implementations for new fields.
- Simplify subchat interaction in `autonomy.rs`, removing unused logic.
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

Successfully merging this pull request may close these issues.

2 participants