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

Implement Katana Runner in Dojo #1205

Merged
merged 33 commits into from
Dec 10, 2023

Conversation

neotheprogramist
Copy link
Collaborator

@tarrencev tarrencev force-pushed the main branch 7 times, most recently from 6fa9022 to ed21620 Compare November 27, 2023 02:45
Copy link
Contributor

@tarrencev tarrencev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the katana runner shouldn't need to introduce a new binary. we already build on as part of katana. the runner should be a simple rust library that calls the katana binary through the shell, supports configuring cli (can all be default for the initial impl), handles forwarding logs to stderr and tears down the instance when it goes out of scope

Cargo.toml Outdated Show resolved Hide resolved
crates/katana/runner/Cargo.toml Outdated Show resolved Hide resolved
@@ -78,7 +78,8 @@ jobs:
toolchain: ${{ env.RUST_VERSION }}
- uses: Swatinem/rust-cache@v2
- uses: arduino/setup-protoc@v2
- run: cargo run --bin sozo -- --manifest-path crates/dojo-core/Scarb.toml test
- run: curl -L https://install.dojoengine.org | bash && source /home/runner/.bashrc && echo $PATH && /home/runner/.config/.dojo/bin/dojoup
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perhaps it makes sense to use the dojo docker image for this job? it comes with katana installed

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That definitely makes sense.

By the way I noticed that dojoup is downloaded to /home/runner/.config/.dojo/bin/dojoup, not sure if it's the expected behaviour

@@ -26,6 +26,12 @@ jobs:
repo-token: ${{ secrets.GITHUB_TOKEN }}
- name: Install nextest test runner
uses: taiki-e/install-action@nextest

- name: Build and run dev container task
uses: devcontainers/[email protected]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm can we use the prebuilt one? we might have to update it (and eventually automate it)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, just trying it out for now

@matzayonc matzayonc force-pushed the 2-katana-runner branch 2 times, most recently from c16d112 to 0f973d0 Compare December 1, 2023 07:26
@tarrencev tarrencev force-pushed the main branch 2 times, most recently from dd36cf5 to 4979471 Compare December 1, 2023 08:56
@tarrencev tarrencev force-pushed the 2-katana-runner branch 2 times, most recently from f583481 to 6242f7f Compare December 1, 2023 10:26
@tarrencev tarrencev force-pushed the main branch 3 times, most recently from 87475da to 112cce7 Compare December 4, 2023 03:03
@tarrencev tarrencev force-pushed the 2-katana-runner branch 5 times, most recently from ee9e365 to 4e0407c Compare December 9, 2023 19:17
@tarrencev tarrencev force-pushed the main branch 5 times, most recently from 6a784ce to a08f2cb Compare December 10, 2023 03:06
@tarrencev tarrencev merged commit 3ce6d26 into dojoengine:main Dec 10, 2023
9 checks passed
@matzayonc matzayonc deleted the 2-katana-runner branch January 10, 2024 14:43
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.

Implement Katana Runner in Dojo
3 participants