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.

Sign up for GitHub

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

Jump to bottom

feat: Migration from coupled server to engine - Python Sub System #534

Closed
tikikun opened this issue Apr 25, 2024 · 2 comments
Closed

feat: Migration from coupled server to engine - Python Sub System #534

tikikun opened this issue Apr 25, 2024 · 2 comments
Labels
type: feature request A new feature
Milestone
v1.0.0

Comments

@tikikun
Copy link
Contributor

tikikun commented Apr 25, 2024

Problem
Currently @CameronNg is working on Python sub system, but we are in the process of migrating to a more decoupled project.

@CameronNg needs to refactor it to a single component backend, first version is being implemented by @vansangpfiev

Success Criteria
Run alongside with other backends like llama cpp etc, as an engine
@tikikun tikikun added the type: feature request A new feature label Apr 25, 2024
@tikikun
Copy link
Contributor Author

tikikun commented Apr 25, 2024

current PR

#505

@tikikun tikikun mentioned this issue Apr 25, 2024
Closed
@Van-QA Van-QA added this to the Cortex v0.4.0 milestone May 9, 2024
@CameronNg CameronNg mentioned this issue May 9, 2024
Merged
@louis-jan
Copy link
Contributor

It's now cortex.python-rt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: feature request A new feature
Projects
Jan & Cortex
Archived in project
Milestone
v1.0.0
Development

No branches or pull requests
4 participants
@tikikun @Van-QA @louis-jan @CameronNg