# Description
Please include a summary of the change and which issue is fixed. Please
also include relevant motivation and context. List any dependencies that
are required for this change.
This path fix some of typos using typos just an example
using tools https://github.com/crate-ci/typos
# How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details
for your test configuration
# Snapshots:
Include snapshots for easier review.
# Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have already rebased the commits and make the commit message
conform to the project standard.
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] Any dependent changes have been merged and published in downstream
modules
Close #issue2277
# Description
fix rag knowledge process workflow template error
# How Has This Been Tested?
run rag knowledge process workflow template
# Snapshots:
Include snapshots for easier review.
# Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have already rebased the commits and make the commit message
conform to the project standard.
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] Any dependent changes have been merged and published in downstream
modules
# Description
Closes#2495
# How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details
for your test configuration
# Snapshots:
Include snapshots for easier review.
# Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have already rebased the commits and make the commit message
conform to the project standard.
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] Any dependent changes have been merged and published in downstream
modules
# Description
**Compatible with Linux and Windows Subsystem for Linux (WSL)
environments only.**
- Add VS Code devcontainer development environment configuration
- Use VS Code's **Dev Container** extension to build a containerized
development environment. Leverage the `eosphorosai/dbgpt:latest` image
as the development environment to avoid repeated dependency
installations and improve development efficiency.
- Follow the guide [Developing inside a
Container](https://code.visualstudio.com/docs/devcontainers/containers)
to set up the Dev Container:
- Install the **Dev Containers** extension.
- Use the shortcut `Ctrl+Shift+P` to open the command palette, then
enter `Dev Containers: Open Folder in Container`.
- Set git ssh
[sharing-git-credentials](https://code.visualstudio.com/remote/advancedcontainers/sharing-git-credentials)
- Before the first launch, please execute the .devcontainer/init_env.sh
script in the project root directory in **host**.
# How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details
for your test configuration
# Snapshots:
Include snapshots for easier review.
# Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have already rebased the commits and make the commit message
conform to the project standard.
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] Any dependent changes have been merged and published in downstream
modules
Close #issue2484
# Description
Fix Chroma Collection name rules
"(1) contains 3-63 characters, "
"(2) starts and ends with an alphanumeric character, "
"(3) otherwise contains only alphanumeric characters, underscores or
hyphens (-), "
"(4) contains no two consecutive periods (..) and "
"(5) is not a valid IPv4 address, "
# How Has This Been Tested?
# Snapshots:
create knowledge name rule as below.
"(1) contains 3-63 characters, "
"(2) starts and ends with an alphanumeric character, "
"(3) otherwise contains only alphanumeric characters, underscores or
hyphens (-), "
"(4) contains no two consecutive periods (..) and "
"(5) is not a valid IPv4 address, "
# Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have already rebased the commits and make the commit message
conform to the project standard.
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] Any dependent changes have been merged and published in downstream
modules
Close#2484
# Description
fix issue 2484
# How Has This Been Tested?
create knowledge space with Chinese
# Snapshots:
Include snapshots for easier review.
# Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have already rebased the commits and make the commit message
conform to the project standard.
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] Any dependent changes have been merged and published in downstream
modules
# Description
1. Support model icons
2. Automatically generated configuration documentations
3. Automatically translated internationalized documents in multiple
languages
# How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details
for your test configuration
# Snapshots:
Include snapshots for easier review.
# Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have already rebased the commits and make the commit message
conform to the project standard.
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] Any dependent changes have been merged and published in downstream
modules
# Description
1. Support OSS and S3 storage backend
2. Add specific configurations for each application
3. Native applications support memory configuration based on window size
for conversation turns and token count
4. Web pages support rendering of LaTeX mathematical formulas
5. DuckDB supports installing plugins from custom local plugin paths
(for offline environments)
6. Fixed Chroma configuration error
Closes#2475Closes#2468Closes#2451Closes#2416
# How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details
for your test configuration
# Snapshots:
Include snapshots for easier review.
# Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have already rebased the commits and make the commit message
conform to the project standard.
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] Any dependent changes have been merged and published in downstream
modules
