-
Notifications
You must be signed in to change notification settings - Fork 452
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
[docs] added touchups to readme.md #354
Conversation
@om-raheja is attempting to deploy a commit to the AIOS Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The v0.2.0.beta version is used to tag and package code to a stable version without changing, and the 0.2.0.beta is currently used for testing. Once the testing is completed, it will be taged and released as v0.2.0.
But is that really necessary for the average person who wants to get
started as fast as possible and get working on the project?
…On Sat Nov 30, 2024 at 3:07 PM EST, Kai Mei wrote:
@dongyuanjushi commented on this pull request.
The v0.2.0.beta version is used to tag and package code to a stable version without changing, and the 0.2.0.beta is currently used for testing.
|
It might be more helpful to add an instruction here to indicate that it is recommended to use the stable version (v0.2.0.beta for example) instead of removing the git checkout -b v0.2.0.beta? |
Sounds good, done.
…On Sat Nov 30, 2024 at 10:01 PM EST, Kai Mei wrote:
> But is that really necessary for the average person who wants to get started as fast as possible and get working on the project?
> […](#)
> On Sat Nov 30, 2024 at 3:07 PM EST, Kai Mei wrote: @dongyuanjushi commented on this pull request. The v0.2.0.beta version is used to tag and package code to a stable version without changing, and the 0.2.0.beta is currently used for testing.
It might be more helpful to add an instruction here to indicate that it is recommended to use the stable version (v0.2.0.beta for example) instead of removing the git checkout -b v0.2.0.beta?
|
Could you change your current changes of git checkout v.20 to git checkout v0.2.0.beta (v0.2.0.beta is the correct tag that needs to be switched to)? |
update README.md
* update * update README.md * update
* Update README.md * Update README.md * Create test.yml
…383) * Update test.yml * Update test.yml
update figures and readme
* update README * update README * update README
1) The assert (requiring the name "ollama" within the model_name is unnecessary and actually prevents normal operation). For example using phi3.5:latest in ollama neither has the name ollama in it nor needs that name. 2) rather than using the chat_result from line 59, it was using an undefined variable 'response' in two places causing an exception.
* feat: enhance API key documentation and display * feat: enhance API key documentation and display * feat: enhance API key documentation and display * feat: enhance API key documentation and display * feat: enhance API key documentation and display * feat: enhance API key documentation and display * Enhanced Error Message dded better error logs in kernel.py to help find bugs faster. ## Changes Made 1. Added clear headers to show where we are in the code: - Tool Manager setup - Agent submission - Agent status checking 2. Made error messages better: - Clear error messages - Stack traces - Basic info like Agent ID Now it's easier to: - See what the code is doing - Find where errors happen - Fix problems quickly * fix: improve agent loading and error handling - Add debug logs to track agent loading - Fix config handling in agent manager - Update seeact_demo_agent config format The code now: - Shows better error messages - Loads agents more reliably - Keeps full config when packaging" * Delete agent.py
* Update test.yml * Update test.yml * Update test.yml
* update test ollama workflow * update * update * fix api key setup for open-sourced models * fix ollama serve command
…#391) * feat: enhance API key documentation and display * feat: enhance API key documentation and display * feat: enhance API key documentation and display * feat: enhance API key documentation and display * feat: enhance API key documentation and display * feat: enhance API key documentation and display * Enhanced Error Message dded better error logs in kernel.py to help find bugs faster. ## Changes Made 1. Added clear headers to show where we are in the code: - Tool Manager setup - Agent submission - Agent status checking 2. Made error messages better: - Clear error messages - Stack traces - Basic info like Agent ID Now it's easier to: - See what the code is doing - Find where errors happen - Fix problems quickly * fix: improve agent loading and error handling - Add debug logs to track agent loading - Fix config handling in agent manager - Update seeact_demo_agent config format The code now: - Shows better error messages - Loads agents more reliably - Keeps full config when packaging" * Delete agent.py * Add Configuration Management and Refresh Option for AIOS Kernel Description: Introduced a configuration file to manage global parameters for the AIOS kernel. Updated the kernel to read parameters from this configuration file at launch. Added a "refresh" command to reload and apply configuration changes without restarting the kernel. Improved API key handling with secure masking in logs. Enhanced error handling and logging for better debugging. * Update .gitignore * Update launch.py * Update google.py * implement refresh command * Update config.yaml * Update
This change is a documentation change that remove the requirement to use
git checkout v.20
and clears up certain information on theREADME.md
that confused me when I first started.