#prompting and using your current module

1 messages · Page 1 of 1 (latest)

young plover
#

trying to get this setup to work. Here's the code at the moment: https://github.com/kpenfound/hello-dagger/pull/2/files#diff-4dd1e2eb1e1e6c8b3af016607bc4ebdaa89bb54c988875e5bf1a8a616dd0f490R84

The goal is to use the current module's Test function with an agent since that's the best selling point of using dagger for agents in a daggerized project

I think there's 3 options here

#

in the PR I linked above. gpt-4.1 is consistently calling Test incorrectly from the privileged env. Maybe it's a privileged thing or maybe an optional argument thing, but here's what it's calling:

:robot: test(HelloDagger: HelloDagger#1, source: Workspace#2)

@bright plover have you tested with privileged envs much?

bright plover
#

not much, no - there isn't an eval for it, it's mostly thought of as a driver for shell still

#

(also trace links are always 1000% preferable to individual snippets)

young plover
#

yeah eventually. I need to figure out the prompting to get it more consistent. But also without making the prompt leak too much dagger implementation ideally

bright plover
#

also that description is pretty unhelpful, it's describing the DirectoryID type instead of the arg - which I guess has no description, but might be better to just omit it in that case

young plover
#

oh I totally glossed over the fact that I didn't have a description on that. I'll update that now

bright plover
#

hmm i wonder if this is specific to contextual dir args too

#

like on paper it looks like it's doing the right thing

#

looking into it!

young plover
#

Thanks I'll keep trying prompts!

young plover
#

yeah if I drop the defaultPath it works great

bright plover
#

looks like it's a bug with handling optional IDs

young plover
#

nice! building

young plover
bright plover
#

not the first time i've seen that behavior pattern

#

wonder what causes it thinkspin

#

should probably disable the HTML sanitization for our JSON responses (<> => unicode escapes): {"result":"/* color palette from \u003chttps://github.com/vuejs/theme\u003e *

#

it's also possible these JSON responses actually just suck for long content

young plover
#

Yeah I've seen that a few times too. It's weird that if I just start a new session and try again it'll have no problem with the same file

bright plover
#

@young plover pushed removal of {"result":"..."} wrapper if you wanna give that a go

young plover
#

maybe it's dead? time="2025-04-23T19:27:36Z" level=error msg="healthcheck failed fatally" client_hostname=dagger client_id=2eqh7lr8zyi25xc4svaz4d1n6 session_id=xgoeh5w47ckci3s89k7mxqcp7

bright plover
#

lol for me it tends to call itself and deadlock

image.png
#

@young plover pushed some more tweaks if you wanna try

#
  1. Validate types earlier to avoid that giant error barf
  2. Add a default description for ID args
young plover
#

sweet, rebuilding

#

rebuilds are so fast on my new setup 🔥

bright plover
young plover
bright plover
#

still HTML escaped too - you sure this is with a new engine?

young plover
# 
> _EXPERIMENTAL_DAGGER_RUNNER_HOST=docker-container://dagger-dev ~/bin/dagger version
dagger v0.18.5-250423135820-750eb1f18adf (docker-container://dagger-dev) darwin/arm64

> docker exec dagger-dev dagger version
dagger v0.18.5-250423135820-750eb1f18adf (unix:///run/dagger/engine.sock) linux/arm64
bright plover
young plover
bright plover
young plover
#

maybe I'm doing something wrong but when I add ?debug I'm not actually getting the debug view 🤔 Its worked fine before though

#

oh duh, i am dumb

bright plover
#

&debug vs ?debug? 😛

young plover
#

yup lol

bright plover
#

still looks like an old engine to me

young plover
#

so weird, what could cause that? the build version looks correct

#

but then it shouldn't have the new commit in the build

#

oh right so I've done 3 builds but there's only 2 commits on that PR. Did you push the last change?

bright plover
young plover
#

that explains it 🤣 rebuilding now