#filesystem

1 messages · Page 1 of 1 (latest)

knotty silo
#

This errors in empty disjunction:

package main

import (
    "dagger.io/dagger"
)

dagger.#Plan & {
    client: filesystem: "./dir": write: contents: actions.build.foo.output
    client: filesystem: "./dir": write: contents: actions.build.bar.output

    actions: build: {
        foo: dagger.#WriteFile & {
            input: dagger.#Scratch
            contents: "foo"
            path: "foo.txt"
        }
        bar: dagger.#WriteFile & {
            input: dagger.#Scratch
            contents: "bar"
            path: "bar.txt"
        }
    }
}

Can you help describe what you were doing in a simple repro case so we can file it?

radiant rampart
#

dagger project update hangs for me

knotty silo
#

Ok, thanks!

#

Can you try changing one of the paths so you can dagger project update, and then change back to the same path to test dagger do build?

#

If it's a clean dir, you need dagger project init before dagger project update.

radiant rampart
#

I tried to stick in in the root of the dagger project

#

I'm still struggling with this project always reporting cannot find package "dagger.io/dagger"

#

lemme try a completely clean dir

#

there we go.

dagger do build
[✔] actions.build.bar                                                                                                                           0.1s
[✔] actions.build.foo                                                                                                                           0.1s
9:09AM FTL failed to execute plan: client.filesystem."./dir".write: 5 errors in empty disjunction:
client.filesystem."./dir".write.contents: 4 errors in empty disjunction:
client.filesystem."./dir".write.contents: conflicting values string and {$dagger:{fs:{_id(dagger.io/dagger):"b70767c3-802b-445a-a6d4-b6bd4f7e0e07"}}} (mismatched types string and struct):
    C:\temp\fstest\cue.mod\pkg\dagger.io\dagger\plan.cue:85:13
    C:\temp\fstest\fstest.cue:7:1
    C:\temp\fstest\fstest.cue:9:51
client.filesystem."./dir".write.contents.$dagger.fs._id: 2 errors in empty disjunction:
client.filesystem."./dir".write.contents.$dagger.fs._id: conflicting values "b70767c3-802b-445a-a6d4-b6bd4f7e0e07" and "c6acfb51-5cb5-4d2f-9ab6-f73526c72697":
    C:\temp\fstest\fstest.cue:7:1
    C:\temp\fstest\fstest.cue:8:51
    C:\temp\fstest\fstest.cue:9:51
client.filesystem."./dir".write.contents.$dagger.fs._id: conflicting values "c6acfb51-5cb5-4d2f-9ab6-f73526c72697" and null (mismatched types string and null):
    C:\temp\fstest\cue.mod\pkg\dagger.io\dagger\fs.cue:63:10
    C:\temp\fstest\cue.mod\pkg\dagger.io\dagger\types.cue:10:29
    C:\temp\fstest\fstest.cue:7:1
    C:\temp\fstest\fstest.cue:8:51
knotty silo
#

Ok, so your issue is with project update, not the conflicting filesystem. Unless you were doing something different for dagger do to hang?

radiant rampart
#

I'm clearly it has to be something about the version of the files in cue.mod. This is the first time I've init a project with the 0.2.1 windows binary.

knotty silo
#

Ok, but previously you said "Multiple writes to a single filesystem can cause unexpected results.". Do you have something to report on that?

radiant rampart
#

No. That was partially based on your comments that I shouldn't do it.

#

The hang might be fixed in a newer pkg version that I just wasn't using.

knotty silo
#

Oh ok. Just to be clear, it's not that it's not recommended, it shouldn't even be possible.

radiant rampart
#

I was working on the config with a combination of Linux and Windows binaries from both 0.2.0 and 0.2.1. Not really a good scenario for reliable outcomes.

knotty silo