#0.17.0-llm.3 🧵
dapper gyro
@woven hound getting a merge conflict with main around cmd/dagger/shell.go
expected?
if you want, we can wait until tomorrow to tag
dapper gyro
merging
woven hound
how about i just push a merge, you can tag that, and then tomorrow or whenever I finish the shell-bbt stuff I can rebase
have the conflict resolved locally
dapper gyro
sure works for me 👍 as long as we can keep pushing to llm proper
woven hound
(non-force) pushed
ivory coral
hm look like the cli publish failed
bleh, goreleaser issues again
it's also failing on main, will fix
dapper gyro
@ivory coral I don't see any commits on main from today
This is the last I see:
commit cb77cc8da722f69dded2d4e59a14212ef9a02243 (main)
Author: Erik Sipsma <erik@dagger.io>
Date: Tue Feb 25 13:10:07 2025 -0800
dapper gyro
Oh no
$ git pull
Updating cb77cc8da..3b2687279
error: Unable to create '/Users/shykes/git/github.com/dagger/dagger/.git/index.lock': File exists.
I'm going to make an educated guess that this is a me problem
ivory coral
Uh oh, yeah that looks like something corrupt in your local git repo
If there's no git process running (e.g. a rebase in process or such), then you should be safe to delete it I think?
dapper gyro
@ivory coral looks like it was a fluke
dapper gyro
FYI @woven hound @unborn bluff I'm holding on tagging anything until you tell me it's clear to do so
unborn bluff
I reverted the filesystem navigation commit in the llm branch because it was throwing a panic, but @woven hound is working on a fix.
woven hound
merged the fix into llm (shell-bbt also updated)`
dapper gyro
@woven hound should I tag? 🙂
woven hound
<@108011715077091328> should I tag? 🙂
have you tried it out? i haven't since helder merged. should be fine, it's up to date with both branches now i think
dapper gyro
Haven't but can try it real quick
dapper gyro
@woven hound I'm getting a weird graphql error when loading github.com/dagger/dagger
Error: find module ".": returned error 422: {"data":null,"errors":[{"message":"Cannot query field \"originalSubpath\" on type \"ModuleSource\".","locations":[{"line":1,"column":35}],"extensions":{"code":"GRAPHQL_VALIDATION_FAILED"}}]}
maybe CLI <-> engine desync? dev CLI with prod/out-of-date/not-rebased engine?
dapper gyro
Update, I'm still struggling, for some reason my usual technique for running dev engine with dagger-in-dagger is not working well:
engine | service llm | upappears to work fine- but
_EXPERIMENTAL_DAGGER_RUNNER_HOST=tcp://localhost:1234 dagger-llm shellfails with "connection refused" and indeed,nc localhost 1234fails to connect also 🤷♂️
OK it works
Testing...
I don't see any change of background when command is running
just the yellow bowtie
woven hound
I don't see any change of background when command is running
do you see a different background for the input when it's focused?
dapper gyro
horrible quality + background sound sorry 😬
I don't see any different background color anywhere
woven hound
i blame zed's terminal emulator - maybe it doesn't support 256 colors, or doesn't make the color distinct? can you try in another terminal?
how does this look? curl -s https://gist.githubusercontent.com/HaleTom/89ffe32783f89f403bba96bd7bcd1263/raw/e50a28ec54188d2413518788de6c6367ffcea4f7/print256colours.sh | bash (not a virus)
could also be that your color scheme has color 0 the same as the terminal background
dapper gyro
woven hound
ah yea it's the 0 there - here's how mine looks
this is one of those annoying things that probably varies a lot from theme to theme... but the background trick looks nice when it works 😭
dapper gyro
so spinner? 🙂
dapper gyro
just an idea - whatever you think is best
woven hound
16 is straight up #000000 which is a bit intense
maybe spinner for redundancy + keep 0 for us enlightened individuals with a tasteful 0 shade in our terminal palette
woven hound
go for it
i have some more fixes but they're very minor (Ctrl+C clearing, Ctrl+D exiting 0)
dapper gyro
Tagged & pushed