-
Notifications
You must be signed in to change notification settings - Fork 184
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
Conversation
6fa9022
to
ed21620
Compare
a28dd33
to
cf687a3
Compare
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 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
.github/workflows/ci.yml
Outdated
@@ -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 |
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.
perhaps it makes sense to use the dojo docker image for this job? it comes with katana installed
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.
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
.github/workflows/ci.yml
Outdated
@@ -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] |
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.
hm can we use the prebuilt one? we might have to update it (and eventually automate 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.
sure, just trying it out for now
c16d112
to
0f973d0
Compare
dd36cf5
to
4979471
Compare
f583481
to
6242f7f
Compare
f6020d4
to
58e4420
Compare
87475da
to
112cce7
Compare
ee9e365
to
4e0407c
Compare
4e0407c
to
1a41979
Compare
6a784ce
to
a08f2cb
Compare
4d441bf
to
ef7cbf3
Compare
fixes neotheprogramist#2