-
Notifications
You must be signed in to change notification settings - Fork 2
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
- feature: refactor runner to use a nodejs backend #27
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
agallardol
commented
Aug 17, 2024
•
edited
Loading
edited
- Replace webpack5 as bundler in favor of esbuild
- Implement Shinkai Tools Backend as a simple and lightweight API to run tools
- Adapt build system to bundle Shinkai Tools Backend as a single binary (nodejs sea + deps + backend code)
- Embed Shinkai Tools Backend binary in Shinkai Tools Runner (rust side)
- Refactor tools in Rust side to be executable using the new nodejs backend
agallardol
had a problem deploying
to
development
August 17, 2024 05:19
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 18, 2024 05:05
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 18, 2024 05:18
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 18, 2024 20:56
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 19, 2024 14:55
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 19, 2024 15:18
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 19, 2024 15:44
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 19, 2024 16:21
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 19, 2024 16:40
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 19, 2024 23:02
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 19, 2024 23:15
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 20, 2024 17:45
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 20, 2024 17:55
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 20, 2024 18:07
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 20, 2024 20:46
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 20, 2024 21:21
— with
GitHub Actions
Failure
agallardol
had a problem deploying
to
development
August 20, 2024 21:26
— with
GitHub Actions
Failure
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.