#github-feed

1 messages ยท Page 27 of 1

vivid lintelBOT
vivid lintelBOT
#

Bumps github.com/moby/buildkit from 0.10.2 to 0.10.3.

Release notes
Sourced from github.com/moby/buildkit's releases.

v0.10.3
https://hub.docker.com/r/moby/buildkit
Notable changes:

Update the builtin Dockerfile frontend to 1.4.2 including a fix for image build contexts
Fix performance regression in builtin Dockerfile frontend on accessing build options #2850

Commits

c8d25d9 Merge pull request #2851 from tonistiigi/picks-v0.10.3
4d4d9cd Resolve dock...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

What is the issue?

When using a non-core (e.g. universe) package, it takes some digging to discover which Definitions a specific package embeds and uses. Given that this use-vs-embed distinction is important, and defines which fields the user must provide concrete definitions for, vs those that are available to use if the user wishes, it would be useful if packages made their external interface more discoverable and more obvious.

One easy way to make it more obvious would be to plac...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

This addresses an issue where the start step execParamsTest was using a
constant cache mount id which was also used by a totally different test.
This made it possible for these tests to interfere with each other.

This also fixes an issue where because we were setting "always" to true
in the sync exec, if the sync exec started before the async one, it would
end up with a not-actually-shared-mount (due to some bizarre but
expected behavior in BuildKit).

The commit fixes all of the ab...

#

Bumps cypress from 9.6.0 to 9.6.1.

Release notes
Sourced from cypress's releases.

9.6.1
Released 5/9/2022
Bugfixes:

Cypress can now launch on systems where Firefox is installed via Snapcraft.
Fixed #19793.
Updates were made to ensure XHR calls are properly displaying the response
body in the command log. Fixed
#21361.
Fixed cy.contains() and
.should(https://github.com/cypress-io/cypress/blob/HEAD/'contain', ...) to handle finding text that
contains ...

vivid lintelBOT
#

What is the issue?

This are great docs for interacting with a docker socket on the client

but users might not know to look for these when they're getting an error like from sam build:

Error: Building image for LambdaFunction requires Docker. is Docker running?

We should explain a bit more when/why you might use this approach generally.
Not sure if there are ot...

vivid lintelBOT
ornate vigilBOT
vivid lintelBOT
#

Fixes https://github.com/dagger/dagger/issues/2413

Overview

I've been assuming that:

  1. dagger project update installs both built-in and external packages
  2. When installing an external package that's already in dagger.sum the checksum is being checked

It's how I think it should work and both turned out be wrong, as I've realized in:

Before

  • dagger project update
    • Copies built-ins from...
vivid lintelBOT
#

There's been a few issues around the limitation of choosing to add flags to the dagger do command that may conflict with the target action's input flags.

How about using a -- to separate command flags from input flags?

dagger do   -- 

Is it possible to split those, so that the command's flags would also only get what's before --?

Example of a (resolved) conflict:

$ dagger do test --param -- --param "foo"
ornate vigilBOT
#

Inspired by yarn and npm.

What if, in addition to dagger do , we could also type dagger for actions that don't clash with built-in command names?

dagger do deploy --prod
dagger deploy --prod

The inspiration comes from yarn/npm which do the same:

yarn run build
yarn build  ## build is actually not a yarn command

This would take one step further the "action inputs as flags" initiative: the entire command becomes user configurable.

The downside is clash with built-...

vivid lintelBOT
#

The DAGGER_CACHE_{FROM,TO} env vars are set by a GHA step and
previously were just passed transparently to our integ tests. However,
after updating those tests to run in dagger, they were not being passed
along anymore.

This just updates ci.cue to explicitly pass them to the integ test
invocation.

In the long-term, it would probably be better to move the setting of
these env vars from a GHA step to within ci.cue. However, right now
since porting the universe tests to run inside da...

vivid lintelBOT
#

What are you trying to do?

Exporting dagger.#Secret directly from export.

For instance

cmd1: docker.#Run & {
  // Command stuff
  export: secrets: "/secrets.txt": dagger.#Secret
}

cm2: docker.#Run & {
  // Command Stuff
  env: SECRET: cm1.export.secrets."/secrets.txt
}

Why is this important to you?

https://github.com/dagger/dagger/pull/2395 is an experimental package for 1password/.
This package required to export secrets as output.

How are you...

vivid lintelBOT
#

What is the issue?

Encountered this while testing CI things in my fork. Seems to be related to cue, but I was not changing anything in dagger code itself (just ci configs):

3:12AM INF actions.test.integration._dag."10"._exec | #26 100.5 not ok 19 plan/client/env optional unset
3:12AM INF actions.test.integration._dag."10"._exec | #26 100.5 # (in test file ./plan.bats, line 207)
3:12AM INF actions.test.integration._dag."10"._exec | #26 100.5 #   `"$DAGGER" "do" -p ./plan/client/en...
ornate vigilBOT
ornate vigilBOT
#

@codecycleteam do you have any javascript scripts or a javascript-based tool/platform that you use today in a CI or deploy process? Looking for good example to use for this suggestion. The example depicted above is basically the Netlify package which uses a shell script that gets executed in a container: https://github.com/dagger/dagger/blob/main/pkg/universe.dagger.io/netlify/netlify.cue#L60-L69

I've se...

vivid lintelBOT
vivid lintelBOT
#

Overview

Upstream

As per #2163 we plan on adopting the upcoming solution from upstream CUE for package management. That solution is modeled closely to how it works in Go. Right now we only have one module field in cue.mod/module.cue, but in the future that file will include everything from a go.mod file, e.g., require, replace, retract, etc.. but with a CUE syntax. It will also have a cue.mod/sum.cue file for checksums...

vivid lintelBOT
ornate vigilBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

What is the issue?

The documentation says:

With Docker running, we are ready to download our example app and run its CI/CD pipeline locally:

git clone https://github.com/dagger/dagger
cd dagger
git checkout v0.2.9

cd pkg/universe.dagger.io/examples/todoapp
dagger do build

The dagger do build command fails for me:

~/dagger/pkg/universe.dagger.io/examples/todoapp #v0.2.9 โฏ dagger do build
failed to load plan: package "universe.dagger.io...
vivid lintelBOT
#

Filed on behalf of Luis T#1639 on Discord:

Hello, I have a question regarding the use of the core.#Cache, what I am trying to do is to create an action that accepts cache as field and pass that field to docker.#Run actions, but can't get it to work, I get an error of empty disjunction.
If instead I create the cache inside the action it works, any recommendation is well appreciated ๐Ÿ™

package vscode
import (
    "dagger.io/dagger"
    "dagger.io/dagger/core"
   ...
#

This sets up Jaeger to run inside GHA during integration tests,
instruments dagger and buildkit to write to it and exports the resulting
data as an artifact of the run.

This enables us to get insight into what actually happened during our CI
runs, which is helpful for debugging and getting insight into the
performance of caching.

Jaeger seems to be mostly designed for "live" use, but it has an
experimental mode for persisting its data to disk, which I use here to
enable exporting ...

vivid lintelBOT
vivid lintelBOT
ornate vigilBOT
#

Hi all!

I'm David Aronchick, and I co-founded Kubeflow. I'm really excited about the opportunity that Dagger is taking on - it's so important to abstract away the details of the orchestration system.

One thing I'm working on right now is an abstraction for ML - specifically taking a Jupyter notebook and pushing it to a number of different backends - it's about to hit 0.2, called the Same Project (https://sameproject.ml/).

Right now, we hardwire in every backend necessary for executi...

vivid lintelBOT
#

Bumps go.opentelemetry.io/otel/exporters/jaeger from 1.4.1 to 1.7.0.

Release notes
Sourced from go.opentelemetry.io/otel/exporters/jaeger's releases.

Release v1.6.3
Fixed

Allow non-comparable global MeterProvider, TracerProvider, and TextMapPropagator types to be set. (#2772, #2773)

Release v1.6.2
1.6.2 - 2022-04-06
Changed

Don't panic anymore when setting a global TracerProvider or TextMapPropagator to itself. (#2749)
Upgrade go.open...

#

Bumps amplitude-js from 8.18.1 to 8.18.2.

Changelog
Sourced from amplitude-js's changelog.

8.18.2 (2022-05-12)
Bug Fixes

assign domain after cookie storage options are given (#528) (2440e9a)
fix perms for github token in release workflow (#532) (195c6ef)
fix release work flow perms to include write access to contents (#533) (c8845ca)
replace String.prototype.includes with String.prototype.indexOf (#530) (b0992f8)
update analytics connect...

vivid lintelBOT
#

What are you trying to do?

I would like to introduce bitbucket on your feature to help manage tasks.

Why is this important to you?

I find bitbucket so cool especially when it comes to pipelines handling.

How are you currently working around this?

am working with a team to improve and come up with a good plugin to collaborate and integrate the two tools for efficient deployment.

vivid lintelBOT
vivid lintelBOT
#

Closes #2375

A new workflow has been created to run the experimental packages "x" inside "universe.dagger.io".
This workflow is named test-experimental-universe.yml and its based on test-universe.yml.

The package.json in the "universe.dagger.io" folder has been modified to add another script to only test the experimental packages and the original "test" script now ignores the tests in folder "x".

Main Makefile has been modified to add a new task for this.

After reviewing...

vivid lintelBOT
#

Closes #2298

After looking in detail for the issue, I noticed that CUE is interpreting absolute paths as package names and not as "local packages".

Since the comment that for now dagger only supports local filesystem paths, I changed the funcion loadPlan to resolve the given path in arguments to a relative path from current working directory. I also checked if a single file is passed in the arguments to resolve this accordingly.

This relative path resolution allows CUE to load all ...

vivid lintelBOT
#

What are you trying to do?

Today, I can use dagger project init -t hello to create a new dagger plan file using a single template available from the upstream dagger repo.

I would like to be able to use template files defined in my own dagger project (or that of another user on github) so that the template can be tailored to my particular needs.

For example, I could run:

dagger project init -t github.com/foo/bar@main:myTemplate

Where myTemplate might match a file or ...

vivid lintelBOT
ornate vigilBOT
ornate vigilBOT
ornate vigilBOT
vivid lintelBOT
#

Bumps google.golang.org/grpc from 1.46.0 to 1.46.2.

Release notes
Sourced from google.golang.org/grpc's releases.

Release v1.46.2
Bug Fixes

client: fix potential panic during RPC retries (#5323)
xds: fix leak of deleted CDS resources from CSDS view (#5339)

Commits

46da11b update version to 1.46.2
10b610c xdsclient/csds: fix leaked metadata (#5339)
1303098 client: fix potential panic during RPC retries (#5323)
beb2eaf Change version to 1.46.1-dev (#52...

#

Bumps concurrently from 7.0.0 to 7.2.0.

Release notes
Sourced from concurrently's releases.

v7.2.0

Support passthrough of additional arguments to commands via placeholders - #33, #282, #307
Add command-{name|index} and !command-{name|index} to --success - #280, #281, #318

New Contributors

@โ€‹paescuj made their first contribution in #317 and #307

v7.1.0

Excluding pattern support added, e.g. concurrently npm:lint:*(!fix) (#305, #306)
Fixed...

ornate vigilBOT
vivid lintelBOT
#

This adds a new core.SendSignal task that enables arbitrary signals to
be sent to an async Start exec. It also adds related support to
core.Stop for specifying a timeout to wait for the exec to exit on its
own before sending SIGKILL.

The main goal here is to support ending Start execs gracefully instead
of being forced to always just SIGKILL them as part of core.Stop.

One immediate goal here to support running Jaeger via core.Start. It
needs to be shutdown gracefully (i.e. with SIG...

vivid lintelBOT
#

Problem

Dagger defines two slightly different concepts: "project" and "plan". This made sense in 0.1 with dagger up, but in 0.2 with dagger do, it is less needed and adds unnecessary complexity to the developer experience.

Solution

Merge the two concepts, and keep only word. I propose to keep the word "project" because it is more familiar to developers.

Details

How it works today

  • A project is a shared context for developping and running Dagger actions. O...
vivid lintelBOT
vivid lintelBOT
#

This adds a makefile UNIVERSE_TESTDIR variable which, when set, will
be passed to find to filter the tests.

Example:

make universe-test UNIVERSE_TESTDIR=x

This will filter out anything under under the x dir in universe.

One can also set something like UNIVERSE_TESTDIR=x/ to test
only packages under a certain author or just UNIVERSE_TESTDIR=alpine
to test the main alpine pacakge.

Signed-off-by: Brian Goff

vivid lintelBOT
#

More recent versions of git include extra safety checks on the owner of
directories before doing any operations on them. This meant that various
calls to git would fail due to being copied from the host, where the
source code is most often not owned by root (the user in the container).

This fixes the issue by just telling git it's okay to use the /src
directory anyways.

Signed-off-by: Erik Sipsma

vivid lintelBOT
ornate vigilBOT
#

Adding some more items:

Cue concepts

  • [ ] Explain how to use intermediate (like a temporary variable) key in a config (store intermediate data in a definition to avoid this value to be exported in a dagger query)
  • [x] Explain the different between a Cue builtin and a definition (native Cue vs dagger stdlib)

Dagger concepts

  • [ ] Explain dagger.#Artifact, why are they special, can be a docker image, a local directory of data, etc...
  • [ ] Explain how to use local c...
#

To add some feedback

I personally find that the developer documentation is lacking a lot of stuff.
To compare it to dockerfile's documentation, the developer documentation is really complete and when you look for a certain instruction, you have few sentences to explain what it does and how to use it and to supplement this, there are few examples to show how to use it that truly help understand it all.
I think that dagger lacks that a lot and that makes dagger harder to take in hand.

A...

vivid lintelBOT
vivid lintelBOT
#

Problem

The Client API is causing a bad developer experience. Developers often report confusion about what itโ€™s for and how it works. Common reasons for the confusion are:

  1. Unfamiliar. Unlike the core action API which works by applying action definitions, the client API works by setting values at a certain path under the client key.
  2. Inconsistent. Read and writes work very differently. ...
ornate vigilBOT
vivid lintelBOT
ornate vigilBOT
vivid lintelBOT
vivid lintelBOT
#

Currently if you redirect stdout via > outfiile or | jq or similar, you get all of the logs in json format from stderr dumped to the screen. Perhaps this is by design, but I was surprised by that given that I only wanted the output to pipe cleanly to jq. To declutter my screen I used standard redirect of stderr to /dev/null: 2>/dev/null.

Example:
From https://docs.dagger.io/1226/handling-outputs#piping-a-result or https://docs.dagger.io/1228/handling-outputs#piping-a-resul...

vivid lintelBOT
#

What is the issue?

Log output

Steps to reproduce

dagger project init
dagger project update
cd cue.mod/pkg/universe.dagger.io/x/solomon@dagger.io
ls

should be two package dirs like in GitHub: https://github.com/dagger/dagger/tree/main/pkg/universe.dagger.io/x/solomon%40dagger.io

spectral
yarn
``
but only one present

yarn


### Dagger version

0.2.11

### OS version

macOS 12.3.1 M1 Arm64
#

What is the issue?

Actions currently have some limitations that should be documented and kept up to date:

caveats:

  • No support for dynamic actions (generate new actions from a conditional data generated at runtime)
  • Actions tasks cannot be nested (#1343)

pattern:

  • How to share code between actions (use of definitions or packages)
  • Action grouping (group several actions under the same key name)
#

Problem

The "todoapp" tutorial used by the Getting Started Tutorial uses yarn, but does not use our own official yarn package (universe.dagger.io/yarn). Instead, it reimplements a custom version with hacks to work around limitations of the official package.

This causes two problems:

  1. The todoapp configuration is more complicated, and less readable, than it should be. This is especially bad because it is the very first example we show t...
#

This is a rewrite of the official yarn package. Improvements include:

  • Usable by the example todoapp plan (which includes a custom inline implementation with hacks). See #2482
  • More granular API
    • #Script to run a yarn script (yarn run ...)
    • #Install to install dependencies (yarn install)
    • #Command to run any command (yarn ...)
  • Proper use of yarn cache, configurable with project name
  • App source code is mounted instead of copied (more efficient)
  • Action con...
vivid lintelBOT
#

Just to add to this, there does not seem to be a way to "bubble up" logs from when commands are executed inside of a docker container. This is really important for diagnosing why a plan is going wrong.

package simple

import (
    "dagger.io/dagger"
    "universe.dagger.io/alpine"
    "universe.dagger.io/docker"
)

dagger.#Plan & {

    actions: {
        image: alpine.#Build & {
            packages: {}
        }
        run_simple: docker.#Run & {
            input: ...
vivid lintelBOT
vivid lintelBOT
#

Bumps github.com/hashicorp/go-version from 1.4.0 to 1.5.0.

Release notes
Sourced from github.com/hashicorp/go-version's releases.

v1.5.0
Includes changeset from hashicorp/go-version#93 and hashicorp/go-version#95

Commits

1a9a0e4 Use encoding TextMarshaler & TextUnmarshaler instead json equivalents (#95)
82485a6 Add json handlers (#93)
45914be Readme: master -> main
50c7800 Update CHANGELOG.md
See full diff in compare view

[![Dependa...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Problem

  • Good: dagger do runs action then prints its output fields. When the terminal is interactive, it prints them in a human-friendly table
  • Bad: the string values in the table are formatted as CUE strings. This makes them harder to read and use, especially multi-line strings (\n are explicitely encoded).

Example:

$ dagger do build
[โœ”] actions.build                                                                                                                      ...
#

Problem

dagger prints most of its output via a standardized logger. This logger is great for producing machine-readable outputs, or sysadmin-friendly log files. But it makes the tool less pleasant to use compared to other command-line client tools. Prefixing every line with a cryptic loglevel code and timestamp, eg. 1:47AM FTL makes the UX worse.

Solution

Print regular outputs to the user like other regular command-line clients; without sacrificing the ability to produce g...

ornate vigilBOT
ornate vigilBOT
vivid lintelBOT
#

Hello, I have a couple of questions:

  1. I have been checking a plan behavior using the tracing.compose.yaml but wanted to see if the span and trace id where logged, so far I can't see them even using the log-level trace, by design those values are not included there?
    Why I am trying to do that? I wanted to play around with the grafana stack, in order to correlate the logs with the traces tempo tries to get the both values from the ingested logs.

  2. Why dagger output is streamed to st...

ornate vigilBOT
#

I think the CUE tutorial is relatively good. However what confused me at start is the relation between CUE and Dagger. A posteriori it looks obvious but it wasn't when I started. Knowing that I'm basically writing a JSON with some tooling (CUE) that then get interpreted by Dagger helped my mental model. To be honest, I'm still a little confused on how dagger generated fields work particularly when referencing them.

vivid lintelBOT
#

Bumps sass from 1.51.0 to 1.52.0.

Release notes
Sourced from sass's releases.

Dart Sass 1.52.0
To install Sass 1.52.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes

Add support for arbitrary modifiers at the end of plain CSS imports, in addition to the existing supports() and media queries. Sass now allows any sequence of identifiers of functions after the URL of an i...

vivid lintelBOT
#

For reasons that are not clear to me at this time, when using the
dagger-debug binary to run universe tests, the new yarn test is
incredibly slow and usually times out after 30 minutes. But when using
the default dagger binary, it's relatively fast.

This needs to be understood better, but for now, running the universe
tests with the default binary will unblock our CI (which currently fails
on this yarn test consistently).

Signed-off-by: Erik Sipsma


@shykes The timeout yo...

vivid lintelBOT
ornate vigilBOT
vivid lintelBOT
vivid lintelBOT
#

Bumps concurrently from 7.2.0 to 7.2.1.

Release notes
Sourced from concurrently's releases.

v7.2.1
What's Changed

Fix --success command- syntax when command name has dashes - #324, #325

Commits

723d7c3 7.2.1
ecbc325 Fix command- syntax capturing for --success (#325)
6f1e11d Update dependencies & declare recommended extensions for VSCode (#320)
See full diff in compare view

[![Dependabot compatibility score](https://dependabot-...

#

Bumps sass from 1.51.0 to 1.52.1.

Release notes
Sourced from sass's releases.

Dart Sass 1.52.1
To install Sass 1.52.1, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
Command Line Interface

Fix a bug where --watch mode would close immediately in TTY mode. This was caused by our change to close --watch when stdin was closed outside of TTY mode, which has been reverted for...

vivid lintelBOT
#

Problem

The dagger.mod and dagger.sum files are being written with a simple fmt.Sprintf(). dagger.mod isn't storing pseudo-versions for branches and in the case of dagger.sum it's also missing the version component.

Solution

I think there's stuff we can reuse from golang.org/x/mod to parse and write these files. Also, make sure to generate pseudo versions for branches.

vivid lintelBOT
#

Problem

CUE only looks for packages in cue.mod/{pkg,gen,usr} (merging these directories). This has required us to commit packages to git.

Solution

Checksums

We do have our own dagger.mod and dagger.sum files. We can make them good enough to be depended on to reinstall packages in new git clones like in CI. This makes committing cue.mod/pkg less necessary.

Global cache

We can take a hint from cuemod, which downloads ...

#

Our dagger.mod file only supports require directives. If we add support for replace, we can use it as a stop-gap for vanity URLs, but also as a better workflow for developing packages, without the need to manually setup links.

Examples:

  • universe.dagger.io => github.com/dagger/dagger/pkg/universe.dagger.io
  • example.com => ~/work/dagger/my-package
#

Bumps amplitude-js from 8.18.2 to 8.18.3.

Changelog
Sourced from amplitude-js's changelog.

8.18.3 (2022-05-24)
Bug Fixes

upgrade to @โ€‹amplitude/ua-parser-js@โ€‹0.7.31 (#535) (7756b52)

Commits

fe44356 chore(release): 8.18.3 [skip ci]
7756b52 fix: upgrade to @โ€‹amplitude/ua-parser-js@โ€‹0.7.31 (#535)
See full diff in compare view

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?depe...

#

Problem

We have a different behavior for built-in packages. dagger.io and universe.dagger.io are embedded in the binary and we have to extract the files from there, fixing the version to the binary version.

Solution

Handle built-in packages like external packages, fetching from git. Then stop embedding these files into the binary.

Todo

Figure out version management (I'll add suggestions later).

vivid lintelBOT
vivid lintelBOT
#

Problem

To keep a project up to date on dependencies, there's a bit of manual work.

Solution

Add a new dagger project tidy command that does the following:

  1. Scan project imports
  2. Add missing requirements to dagger.mod
  3. Remove unused requirements from dagger.mod
  4. Do a dagger project update (installs requirements, verifies checksums)
  5. Remove stuff in cue.mod/pkg that's not being used, or from global cache
  6. Cleanup dagger.sum
vivid lintelBOT
#

Problem

I don't think we're able to install dependencies of dependencies right now (I'll check), which means we need to list everything directly In the project's dagger.mod.

Solution

Check the dependencies' dependencies and use the MVS algorithm on conflicting versions.

vivid lintelBOT
#

Problem

When downloading modules from cue.mod/dagger.mod, we have a regex that tries to match a repo prefix and path suffix from a URL. This has limited capability. It works well enough if you have .git to split them, or if it's GitHub, though.

As for authentication, it assumes a public repo (https) unless a --private-key argument is provided, in which case ssh is used. We need more authentication methods.

We could also benefit from downloading from import path, instead of j...

vivid lintelBOT
#

What is the issue?

After setting a workdir on the image config the #Copy steps writes to '/'. My assumption is that the #Copy and other commands would follow Dockerfile type guidance and respect workdir automatically.

Log output

4:17PM INF system | installing all packages...
4:17PM INF system | installed/updated package dagger.io@0.2.12
4:17PM INF system | installed/updated package universe.dagger.io@0.2.12

dagger do --plan workdir-copy.cue test --log-format=plain
4:22PM INF ...

vivid lintelBOT
ornate vigilBOT
vivid lintelBOT
#

What are you trying to do?

It would be great to be able to hook into the DAG created by dagger to create build steps in a Jenkins that align to visualize the progress of a long running job via Blue Ocean.

Why is this important to you?

Seeing the output visually is often helpful vs just seeing streaming text output.

How are you currently working around this?

I don't see a way to work around this currently. Everything just ends up in a single build step in Jenkins.

vivid lintelBOT
#

This defines:

  • Strongly typed, versioned telemetry events
  • Event format (base properties and event-specific properties)
  • A few events as example
  • Contextual plumbing to be able to push telemetry events from anywhere
  • NOTE: this defines the plumbing and API for typed events, it's not actually pushing anything

Example to send an event:

// telemetry is available through the context (just like the logger)
tm := telemetry.Ctx(ctx)

// pushing a (strongly typed) even...
vivid lintelBOT
#

This PR adds support for workdir with the core.#Copy function. Closes #2512.

What's changed

  • Added a new workdir field to core.#Copy
  • Use the workdir field in plan/task/copy.go to set the inputState.Dir to the working directory.
  • docker.#Copy sets the workdir field based on the image.config.workdir
    *Test cases to verify copying with workdir, without workdir, and with workdir and absolute value.

I played with just cuelang modifications in the docker/build.cue file but had to...

ornate vigilBOT
#

I've managed to build a from-scratch docker container in dagger, but it feels a bit hacky.

I defined scratch by using a FROM SCRATCH repo that I pushed to docker hub:

#Scratch:{
    build: {
        docker.#Build&{
            steps: [
                docker.#Pull&{
                    source: "jcvz/scratch"
                }
            ]
        }
    }
    output: build.output
}

Then, in the full build, I call it as the first build step:

_build_doc...
#

We could have a docker.#Scratch:

#Scratch: docker.#Image & {
    rootfs: dagger.#Scratch
    config: {}
}

But in the meantime you can easily do this:

_build_docker: docker.#Build&{
	steps: [
		{ output: rootfs: dagger.#Scratch },
		docker.#Copy & {
			contents: _build_exe.export.directories."/server"
			dest: "/"
		},
		...
	]
}

Or

_build_docker: docker.#Build&{
	steps: [
		docker.#Copy & {
			input: rootfs: dagger.#Scratch
		...
#

We could have a docker.#Scratch:

#Scratch: #Image & {
    rootfs: dagger.#Scratch
    config: {}
}

But in the meantime you can easily do this:

_build_docker: docker.#Build&{
	steps: [
		{ output: rootfs: dagger.#Scratch },
		docker.#Copy & {
			contents: _build_exe.export.directories."/server"
			dest: "/"
		},
		...
	]
}

Or this:

_build_docker: docker.#Build&{
	steps: [
		docker.#Copy & {
			// input: docker.#Scratch
			input...
vivid lintelBOT
#

This is a very rough prototype of the updates I'm proposing to enable better ways of configuring cache. I'm opening this to get feedback on the design; the code here is just serving as a proof-of-concept to give everyone a rough idea of what this could look like.


Problems Being Solved

This is mentioned in the Seamless Configuration section of the CI caching epic, but to summarize the problems being solved here:

  1. Configuring cac...
vivid lintelBOT
#

Bumps github.com/spf13/viper from 1.11.0 to 1.12.0.

Release notes
Sourced from github.com/spf13/viper's releases.

v1.12.0
This release makes YAML v3 and TOML v2 the default versions used for encoding.
You can switch back to the old versions by adding viper_yaml2 and viper_toml1 to the build tags.
Please note that YAML v2 and TOML v1 are considered deprecated from this release and may be removed in a future release.
Please provide feedback in discussions and...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Bumps @docusaurus/core from 2.0.0-beta.20 to 2.0.0-beta.21.

Release notes
Sourced from @โ€‹docusaurus/core's releases.

2.0.0-beta.21 (2022-05-27)
:boom: Breaking Change

docusaurus-plugin-pwa

#7422 refactor(pwa): remove reloadPopup option in favor of swizzling (@โ€‹Josh-Cena)

create-docusaurus, docusaurus-cssnano-preset, docusaurus-logger, docusaurus-mdx-loader, docusaurus-migrate, docusaurus-plugin-client-redirects, doc...

vivid lintelBOT
ornate vigilBOT
#

Having started using Dagger, I thought about what it would take to add logging to the Dagger APIs to help improve the user experience for other developers working with plans I write. I tinkered for a while and came up with this draft approach.

What's changed

  • Add a dagger.#Logger type.
  • Add a logger definition to the client in plan.
  • Create a core.#Log task that uses logger as an input.
  • The #Log and #Logger type exposes the Dagger CLI logger to the user.

Goals

  • Keep c...
vivid lintelBOT
vivid lintelBOT
#

Bumps cypress-localstorage-commands from 1.7.0 to 2.0.0.

Release notes
Sourced from cypress-localstorage-commands's releases.

Drop NodeJs 12 support
Removed

chore: Drop NodeJs 12 support
docs: Remove Fossa badge

Changed

chore: Remove NodeJs v12 from tests workflow. Add NodeJs v18
chore(deps): Update devDependencies

Changelog
Sourced from cypress-localstorage-commands's changelog.

[2.0.0] - 2022-05-30
Removed

chore: Drop...

vivid lintelBOT
#

What are you trying to do?

Given an action like:

		_alpine: alpine.#Build & {
			packages: bash: _
		}

The output is

6:59PM INF actions._alpine._dag."0"._op | computing
6:59PM INF client.env | computing
6:59PM INF client.env | completed duration=0s
6:59PM INF actions._pull | computing
6:59PM INF actions._pull | completed duration=0s
6:59PM INF actions._alpine._dag."0"._op | completed duration=3.7s
6:59PM INF actions._alpine._dag."1"._exec | computing
6:59PM I...
vivid lintelBOT
#

What is the issue?

With a typo on my dagger project init, I added a character o, it told me all was good, to proceed to dagger project update, but the update failed.

It actually created the cue.mod in the o subfolder.
We should display this info in the first log: Project initialized in ! To install dagger packages, run `dagger project update` from

Log output

$ dagger project init o
Project initialized! To install dagger packages, run `dagger project update`...
vivid lintelBOT
#

What are you trying to do?

I have a monorepo and I'd like to be able to run dagger do from any of the subprojects within the monorepo.

Much like git commit traces up the directory tree to find .git, I'd like dagger do to do the same for cue.mod.

Why is this important to you?

To save me having to run cd ../../../ && dagger do or dagger do -p ../../../

How are you currently working around this?

As above

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Defaulting the user of an exec to "root" causes errors when using images
that don't have /etc/passwd ("distroless" and similar type images).

BuildKit's logic is bit surprising here. If we instead provide
"root:root", then it has a codepath that will automatically default to
using uid/gid 0 without needing to check /etc/passwd or /etc/group.

Signed-off-by: Erik Sipsma

User in discord encountered this, also seems to have been reported previously, fixes #1659

vivid lintelBOT
vivid lintelBOT
#

Bumps google.golang.org/grpc from 1.46.2 to 1.47.0.

Release notes
Sourced from google.golang.org/grpc's releases.

Release 1.47.0
New Features

xds: add support for RBAC metadata invert matchers (#5345)

Bug Fixes

client: fix a context leaked if a connection to an address is lost before it is fully established (#5337)

Special Thanks: @โ€‹carzil

client: fix potential panic during RPC retries (#5323)
xds/client: fix a potential concurrent map read/write in ...

#

Bumps amplitude-js from 8.18.3 to 8.18.4.

Changelog
Sourced from amplitude-js's changelog.

8.18.4 (2022-05-31)
Bug Fixes

polyfill object entries for ie11 (#536) (9e68a45)

Commits

67748c6 chore(release): 8.18.4 [skip ci]
9e68a45 fix: polyfill object entries for ie11 (#536)
See full diff in compare view

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=amplitude-...

#

Bumps cypress from 9.7.0 to 10.0.0.

Release notes
Sourced from cypress's releases.

v10.0.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-0-0

Commits

02148ac release 10.0.0 [skip ci]
e0e5a60 fix: prevent adding default supportFile on migration (#21985)
ae8d4b2 fix: cleanup test flake (#21989)
566a7b1 fix: UNIFY-1774 error if component config is not sourced for webpack/vite (#2...
996823c fix: support loading config files for pr...

vivid lintelBOT
#

Right now core.#Dockerfile doesn't seem to support secret mounts: https://github.com/moby/buildkit/blob/master/frontend/dockerfile/docs/syntax.md#run---mounttypesecret

The way this should work is that users should be able to configure, in CUE, a mapping of secret IDs to secret contents. Then, anytime their Dockerfile requests a mount for a secret with that ID, it should show up as expected.

This should be straightforward, the "secret id"->"secret values" mappings can just be plugged i...

#

What are you trying to do?

get list of files in a directory by supplying a FS, a path, and an optional glob pattern.

Why is this important to you?

from @rockyburt:

...the particular use case i have is that when i run the standard python build command to generate a sdist (source distribution) i won't know what the name of that file is until it's actually generated, so the canonical way to get the name of that file would be ls *.tar.gz it will be the only file in the dist d...

vivid lintelBOT
#

What is the issue?

We don't have clear docs on how to use "Dagger project init help". A user wanted to create a new cue file, but didn't see how to do this with Dagger project init. @marcosnils explained that they could use "dagger project init help" command to do this.

We should make this more clear in the docs, so it is easier for our users to find.

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Before this, core.Start output was just dropped entirely. Now, its
stdout and stderr are logged in the same way core.Exec output is
logged.

This requires importing some Buildkit code that it uses for collecting
and publishing log streams efficiently (internally uses a circular
buffer). The interface is a bit clunky but gets us parity between
core.Start and core.Exec.

Signed-off-by: Erik Sipsma

Note: this also has a separate commit that refactors the code to split it amongst sep...

vivid lintelBOT
#

Bumps cypress-localstorage-commands from 2.0.0 to 2.1.0.

Release notes
Sourced from cypress-localstorage-commands's releases.

Support Cypress 10
Changed

chore: Update Cypress devDependency to v10
test: Use Cypress v10 for running plugin e2e tests. Update configuration.
chore: Update github actions versions

Changelog
Sourced from cypress-localstorage-commands's changelog.

[2.1.0] - 2022-06-02
Changed

chore: Update Cypress ...

#

Bumps cypress from 9.7.0 to 10.0.1.

Release notes
Sourced from cypress's releases.

v10.0.1
Changelog: https://docs.cypress.io/guides/references/changelog#10-0-1
v10.0.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-0-0

Commits

013501c release 10.0.1 [skip ci]
ea3cd7f Merge branch 'master' into develop
9caf623 fix: do not show incorrectly support file migration step (#22015)
d875564 fix: prevent RunCard styles from leaking (#22...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
ornate vigilBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

What are you trying to do?

I am trying to update the PATH variable based on its previous value inside docker.#Build. docker.#Set is insufficient for it. A mechanism to update env values or PATH specifically should be abstracted away as an action for ease in translation.

Why is this important to you?

Various pieces of software demand the PATH variable be updated for global discovery.
ENV PATH=${PATH}: is a common occurrence in most Dockerfiles, but it is extremely convoluted to do ...

vivid lintelBOT
#

Bumps cypress from 9.7.0 to 10.0.2.

Release notes
Sourced from cypress's releases.

v10.0.2
Changelog: https://docs.cypress.io/guides/references/changelog#10-0-2
v10.0.1
Changelog: https://docs.cypress.io/guides/references/changelog#10-0-1
v10.0.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-0-0

Commits

9407d07 release 10.0.2 [skip ci]
309c31f fix: changes to correct typescript detection behavior (#22058)
3b5a245 fix: sanitize...

#

Bumps sass from 1.52.1 to 1.52.2.

Release notes
Sourced from sass's releases.

Dart Sass 1.52.2
To install Sass 1.52.2, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes

Preserve location of trailing loud comments (/* ... */) instead of pushing the comment to the next line.

See the full changelog for changes in earlier releases.

Changelog
Sourced from sass's changelog.

1...

vivid lintelBOT
vivid lintelBOT
#

What is the issue?

After using docker.#Set & { config: env: : } once inside a docker.#Build, all default environment variables such as PATH, and HOME become inaccessible for interpolation. They exist inside the resultant image when a container is spun up to check.

Log output

9:22PM ERR system | failed to load plan: actions.test._build._dag."2"._set.config.env.PATH: invalid interpolation: undefined field: PATH:
./main.cue:19:24
./main.cue:19:52
actions.test._build._dag."...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Bumps github.com/stretchr/testify from 1.7.1 to 1.7.2.

Commits

41453c0 Update gopkg.in/yaml.v3
285adcc Update go versions in build matrix
6e7fab4 Bump actions/setup-go from 2 to 3.1.0
106ec21 use RWMutex
a409ccf fix data race in the suit
3586478 assert: fix typo
7797738 Update versions supported to include go 1.16
See full diff in compare view

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dep...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

What are you trying to do?

I created a main.cue and imported the github.com/mlkmhd/dagger-maven project in it, but it does not resolve my dependency when I run dagger project update command:

main.cue:

package main

import (
    "dagger.io/dagger"
    "dagger.io/dagger/core"
    "github.com/mlkmhd/dagger-maven"
)

dagger.#Plan & {
...

I run this command:
$ dagger project update

but it does not resolve imported dependency ...

vivid lintelBOT
#

Bumps github.com/rs/zerolog from 1.26.1 to 1.27.0.

Commits

e9344a8 docs: add an example for Lshortfile-like implementation of CallerMarshalFunc ...
263b0bd #411 Add FieldsExclude parameter to console writer (#418)
588a61c ctx: Modify WithContext to use a non-pointer receiver (#409)
361cdf6 Remove extra space in console when there is no message (#413)
fc26014 MsgFunc function added to Event (#406)
025f9f1 journald: don't call Enabled before each write (#407)
...

vivid lintelBOT
vivid lintelBOT
#

Problem

When running dagger do --help on a valid plan, I see the following error:

$ dagger do --help
panic: event: Action cannot be empty

goroutine 1 [running]:
go.dagger.io/dagger/telemetry.(*Telemetry).Push(0xc00046ae70, {0x3?, 0xc003e3f9b8?}, {0x1493fd8?, 0xc002940b80?})
        /src/telemetry/telemetry.go:88 +0x11e
go.dagger.io/dagger/cmd/dagger/cmd.glob..func2(0x1cabcc0, {0xc000122200, 0x1, 0x1})
        /src/cmd/dagger/cmd/do.go:91 +0x70c
github.com/spf13/cobra....
#

Problem

Deploying a Dagger project to CI, like Gitlab, Github Actions or Jenkins, is a manual and fastidious process. It is not "fire and forget": future changes to the Dagger project will often require changes to the CI configuration calling it as well. This adds friction to our DX, and creates the risk of drift and manual error.

Solution

dagger should support generating native CI configurations for a given project. For example dagger project build --target github, `dagger...

vivid lintelBOT
#

What is the issue?

Hello,
I looked at the Gitlab example here (which works btw) and wondered why curl is installed for fetching the dagger install.sh instead of just using wget, which is natively available in Linux systems. I am no expert in this matter, but this seems like unnecessary overhead for me.

If using wget, this line could be removed:
- apk add --no-cache curl

and the curl line could be replaced with `wget -O - https://dl...

ornate vigilBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

What are you trying to do?

Clearly export and see errors from a Dagger do execution using a standard format. Someone I talked to after my PlatformCon talk mentioned this as a good way to integrate with existing systems:

Usually an HTML or something like JUnit XML, which can be displayed in most of the CI/CD web interfaces.

They in the past have struggled with trying to parse errors out of BuildKit's (custom, non-standard) output, something like this seems like it would help them a ...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Bumps sass from 1.52.1 to 1.52.3.

Release notes
Sourced from sass's releases.

Dart Sass 1.52.3
To install Sass 1.52.3, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes

Fix crash when trailing loud comments (/* ... */) appear twice in a row across two different imports which themselves imported the same file each.

See the full changelog for changes in earlier releases.
Dart...

vivid lintelBOT
#

Dagger Cloud run URL

https://dagger.cloud/runs/38b70464-c8b4-4be0-8342-15ad9872ec15

What happened? What did you expect to happen?

The referenced run was successful, but not quite what I was trying to do.
Apparently the telemetry wasn't getting uploaded for my failed runs.

In any case, this is what I was actually trying to do:

package main

import (
  "dagger.io/dagger"
  "dagger.io/dagger/core"
)

_alpine: core.#Pull & { source: "alpine:latest" }

#cfgs: {
  _pa...
#

What is the issue?

Users aren't sure how to use registries other than Docker Hub with core.#Pull/#Push and docker.#Pull/#Push. Docker Hub which might be rate-limiting/throttling them, or they might have an org requirement to use their registry. Common ones will be AWS ECR, Azure ACR, Google GCR, GitHub Container Registry.

package main

import (
    "dagger.io/dagger"
    "universe.dagger.io/docker"

)

dagger.#Plan & {
    _awsRegion: "us-east-1"

    client: {
...
vivid lintelBOT
#

What is the issue?

Since it's complicated to get package management right and we'd love folks to share their creations with the whole Dagger community via Universe, it's easiest if they develop their packages right in a Universe context versus in a disconnected repo.

To that end we'd recommend creating a fork of dagger/dagger, creating a branch for their new package, then putting it under universe.dagger.io/x// and taking advantage of the cue.mod already governing the `universe...

vivid lintelBOT
#

What is the issue?

cannot reuse body, request must be retried errors when pushing multiple images back to back?

FTL failed to execute plan: task failed: actions.push."redhat-marketplace-operator".dataservice._opt._push: failed commit on ref "manifest-sha256:b61cb26feed1460415762fe863fa15ac79a64739420dcef0dc9a0bb63b9ce152": cannot reuse body, request must be retried

I'm seeing similar errors here: https://github.com/docker/build-push-action/issues/452
fix suggested by...

vivid lintelBOT
vivid lintelBOT
#

What is the issue?

Any secret outputs generated by pulumi.#Up are exported as the literal string [secret] instead of the actual secret value. I needed to edit the up.sh script to add --show-secrets to work around this issue.

cc @rawkode @sipsma

Log output

No response

Steps to reproduce

No response

Dagger version

dagger devel (6d14bdda) linux/amd64

OS version

Arch Linux

vivid lintelBOT
ornate vigilBOT
#

Hello Dagger Community! ๐Ÿ‘‹

cc @dagger/maintainers

We've been rethinking contribution of content to Dagger Universe and want to share this proposal for comment as we refine the plan. Comments/suggestions welcome. I'll start with the current state and our proposed future.

Up until recently:

There were two kinds of Dagger Universe packages:

  • official ones under universe.dagger.io/
  • experimental ones under universe.dagger.io/x//

Well, maybe three...In addition there wer...

vivid lintelBOT
ornate vigilBOT
#

That's a great proposal! I have few questions:

1 - What about current PRs (#2452, #2533, #2581 and #2578) ? Should they update it or we take care about copying those to alpha?

2 - I do not see kubectl package in Alpha, what is the decision for packages that has multiple implementation?

3 - How will we test packages that interact with third-parties (aws/sam, discord) or required infrastructure (kubernetes, pulumi) ? Is it up to dagger to set infrastructure or to the user? ...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
ornate vigilBOT
#

That's a great proposal! I have few questions:

1 - What about current PRs (#2452, #2533, #2581 and #2578) ? Should they update it or we take care about copying those to alpha?

We should redirect those PRs to alpha

2 - I do not see kubectl package in Alpha, what is the decision for packages that has multiple implementation?

https://github.com/dagger/dagger/pull/2579#issue-1260905491
Packages with competing implementations were not copied yet. We'll need to work with ...

vivid lintelBOT
#

What is the issue?

I tried to pull from a remote git repository which runs with a self signed certificate. Is there a option to add a trusted certificate?

Log output

#1 0.058 Initialized empty Git repository in /var/lib/buildkit/runc-overlayfs/snapshots/snapshots/3/fs/
#1 0.144 fatal: unable to access 'https://gitlab/group/project.git/': SSL certificateโ€ฆ
4:25PM FTL failed to execute plan: task failed: actions.source: failed to load cache key: failed to fetch remote https://gitlab...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

What are you trying to do?

The current design for fetching repos is very limiting. We're parsing a URL into repo and path, but current design assumes 2 parts for the repo and rest for the path.

For example, the URL gitlab.com/dagger/dagger/stdlib/test/test gets parsed into:

  • Repository: github.com/dagger/dagger
  • Path: /stdlib/test/test

I think it's more flexible to require a .git separator in the URL to get the path after it, otherwise making the full URL the ...

vivid lintelBOT
#

cc @samalba

Functionality: PRs to universe.dagger.io/x should be blocked by a check and the copy below should point contributors to alpha instead.

Proposed copy:

Thank you for your submission to Dagger Universe! We've changed the flow for submissions and now all new submission PRs should be targeted to universe.dagger.io/alpha/. More information is here: https://github.com/dagger/dagger/discussions/2616

vivid lintelBOT
#

Bumps concurrently from 7.2.0 to 7.2.2.

Release notes
Sourced from concurrently's releases.

v7.2.2
What's Changed

Update rxjs to version 7.0.0 - #326
Fix TypeScript not able to resolve types when on Node 16 - #330

New Contributors

@โ€‹jsfix-updater made their first contribution in open-cli-tools/concurrently#326
@โ€‹Baune8D made their first contribution in open-cli-tools/concurrently#330

v7.2.1
What's Changed

Fix --success command- syntax w...

vivid lintelBOT
vivid lintelBOT
#

We want to create some starter templates. We will make an issue for each of the templates that we are requesting.

This issue specifically covers the need for a guide that the community can use to build the templates quickly. The output of this issue should be a guide that the community can follow to ensure that all of the starter templates have the same consistency.

Once completed, we will attach this guide to each of the starter template issues as a reference.

Some examples:
ht...

vivid lintelBOT
#

What is the issue?

need to make sure there are docs on these gotchas:
https://cuelang.org/play/?id=JKDWbdkJ5LV#cue@export@cue

template syntax vs array syntax vs string interpolation

template: flags: [string]: string | bool where this would be valid

flags: {
    "--foo": "bar:
    "baz": true
}

vs array: args: [...string] where this would be valid

args: ["foo", "bar", "baz"]

and myarg: args[1] evals to means myarg evals to "bar"

vs string i...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Problem

We allow installing modules with a branch today, but this is giving reproducibility issues. When updating packages today, only git tags are considered for finding latest versions (instead of considering branches). The best fix is to not store branches in dagger.mod but convert to pseudo-versions instead.

This is planned in #2502 but maybe there's a quicker fix we can make to allow some users to update packages using a branch.

Stop-gap solution

When updatin...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
ornate vigilBOT
vivid lintelBOT
#

dagger project init should have an update like dagger project init --update --force that runs a dagger project update --force right after init (--force is proposed new flag). This is useful in a new project or in CI environments.

dagger project update (without --force) should ask the user if they really want to update packages if the project's cue.mod/pkg directory is not empty. This could prevent overwriting WIP dev on packages, etc.

dagger project update --force or `da...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

What is the issue?

Environment variables marked as optional cannot be used as environment variables in actions. For example, the following plan would fail:

package main

import (
	"dagger.io/dagger"

	"universe.dagger.io/alpine"
	"universe.dagger.io/bash"
)

dagger.#Plan & {
	client: env: {
		TEST_OPTIONAL?: dagger.#Secret
	}
	actions: {
		test: {
			run: bash.#Run & {
				_image: alpine.#Build & {
					packages: {
						bash: _
					}
				}
				input: _im...
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Bumps github.com/stretchr/testify from 1.7.2 to 1.7.3.

Commits

07dc7ee Bump actions/setup-go from 3.1.0 to 3.2.0 (#1191)
c33fc8d Bump actions/checkout from 2 to 3 (#1163)
3c33e07 Added Go 1.18.1 as a build/supported version (#1182)
e2b56b3 Bump github.com/stretchr/objx from 0.1.0 to 0.4.0
See full diff in compare view

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/st...

#

Bumps @mdx-js/react from 1.6.22 to 2.1.2.

Release notes
Sourced from @โ€‹mdx-js/react's releases.

2.1.2
Core

7bcd7059 Fix some performance by improving vdom diffing
by @โ€‹0phoff in mdx-js/mdx#2062
f77c33f5 Fix support for baseUrl rewriting import.meta.url
by @โ€‹wooorm in mdx-js/mdx#2021

Docs

3579aa38 Add use of tla in docs
366ddb4d Update examples in readme
63fd208d Add @next/mdx to Next.js getting started guide
by @โ€‹remcohaszing in m...

vivid lintelBOT
#

fixes #2687

This PR further simplifies the left nav, removing the superfluous index pages and starting docs at the local-dev page with more context. More links back to local dev from install and CI. It also simplifies the "what is dagger" and "dagger vs x" pages to one. It moves the CUE and BuildKit benefits to the "dagger vs" page and uses the Dagger CUE explanation page instead of pointing to cuelang.org (the Dagger CUE page has a link there if need, but the Dagger page has better conte...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

What is the issue?

Several users have reported that loading an image into docker takes a very long time. While part of this is inherent (exporting a tarball and loading it into docker can take up a fair bit of memory+cpu), our implementation relies on a lot of extra copying:

  1. It uses core.#Export to export the tarball to a tmp dir on the local filesystem
  2. Then that gets reloaded back into the buildkit with a local import
  3. That local import gets copied (to deal with some cache ...
vivid lintelBOT
#

Bumps github.com/stretchr/testify from 1.7.2 to 1.7.4.

Commits

48391ba Fix panic in AssertExpectations for mocks without expectations (#1207)
840cb80 arrays value types in a zero-initialized state are considered empty (#1126)
07dc7ee Bump actions/setup-go from 3.1.0 to 3.2.0 (#1191)
c33fc8d Bump actions/checkout from 2 to 3 (#1163)
3c33e07 Added Go 1.18.1 as a build/supported version (#1182)
e2b56b3 Bump github.com/stretchr/objx from 0.1.0 to 0.4.0
See...

#

Bumps github.com/spf13/cobra from 1.4.0 to 1.5.0.

Release notes
Sourced from github.com/spf13/cobra's releases.

v1.5.0
Spring 2022 Release ๐ŸŒฅ๏ธ
Hello everyone! Welcome to another release of cobra. Completions continue to get better and better. This release adds a few really cool new features. We also continue to patch versions of our dependencies as they become available via dependabot. Happy coding!
Active help ๐Ÿ‘๐Ÿผ
Shout out to @โ€‹marckhouzam for a big value a...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Bumps cypress from 10.1.0 to 10.2.0.

Release notes
Sourced from cypress's releases.

v10.2.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-2-0

Commits

b907127 chore: updating version (#22432)
181a2b0 Trigger Build
b925dce Merge pull request #22424 from cypress-io/master
6d34fd3 fix: clean up some unexpected behavior and designs (#21551)
152e828 fix(cli): filter CertVerifyProcBuiltin from stderr (#22342)
b865fd4 fix(cli): don't ...

#

Bumps sass from 1.52.3 to 1.53.0.

Release notes
Sourced from sass's releases.

Dart Sass 1.53.0
To install Sass 1.53.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes

Add support for calling var() with an empty second argument, such as var(--side, ).

JS API

Fix a bug where meta.load-css() would sometimes resolve relative URLs incorrectly when called from a mixin using the ...

vivid lintelBOT
#

This commit revert a change of API in universe/go.
A recent PR added 2 fields: name and repository to customize the image to
pull when calling go.#Image.
The problem is that change does not fit with the purpose of go.#Image, this
one should be used as default image to cover simple workflow with the simplest
possible API. That's why it's usually only possible to configure some packages
and a version of the official image.

If the user want to provide a custom image, he can ov...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

to avoid confuse panic https://github.com/dagger/dagger/issues/2326

instead panic

show error like

5:06PM ERROR system | failed to load plan: actions.test.run._exec.env.TEST1: ( dagger.#Secret & client.commands.echo.stdout & (string | dagger.#Secret) & (string | dagger.#Secret) ): actions.test.run._exec.env.TEST1: incomplete cause disjunction: ( dagger.#Secret & client.commands.echo.stdout & (string | dagger.#Secret) & (string | dagger.#Secret) ): actions.test.run._exec.env.TEST1...
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

What are you trying to do?

This maybe be more of a documentation request. But essentially, having a good way to run dagger from within dagger. This should solve issues where dagger with certain command line options (ie --platform) could be run under a command dagger action set.

Use Case:
Steps to run:

  1. build project documentation via one or more dagger actions (only needs to run on default platform)
  2. acquire docker login credentials from a cloud provider for pushing (only nee...
vivid lintelBOT
#

Bumps github.com/stretchr/testify from 1.7.4 to 1.7.5.

Commits

b5ce165 fixing panic in calls to assertion with nil m.mutex (#1212)
c206b2e Mock can be deadlocked by a panic (#1157)
1b73601 suite: correctly set stats on test panic (#1195)
ba1076d Add .Unset method to mock (#982)
c31ea03 Support comparing byte slice (#1202)
See full diff in compare view

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_s...

#

Bumps amplitude-js from 8.18.4 to 8.18.5.

Release notes
Sourced from amplitude-js's releases.

v8.18.5
8.18.5 (2022-06-24)
Bug Fixes

add guard for navigator for use in envs that do no support navigator (#542) (c3b31ad)
fix s3 upload script to use iam role (#534) (a453dc3)

Changelog
Sourced from amplitude-js's changelog.

8.18.5 (2022-06-24)
Bug Fixes

add guard for navigator for use in envs that do no support navigator (#542) (c3b31ad...

vivid lintelBOT
vivid lintelBOT
#

Bumps github.com/hashicorp/go-version from 1.5.0 to 1.6.0.

Release notes
Sourced from github.com/hashicorp/go-version's releases.

v1.6.0
FEATURES:

Add Prerelease function to Constraint to return true if the version includes a prerelease field (#100)

Changelog
Sourced from github.com/hashicorp/go-version's changelog.

1.6.0 (June 28, 2022)
FEATURES:

Add Prerelease function to Constraint to return true if the version includes a prerelease field...

#

Bumps cypress from 10.2.0 to 10.3.0.

Release notes
Sourced from cypress's releases.

v10.3.0
Changelog: https://docs.cypress.io/guides/references/changelog#10-3-0

Commits

61f8bdc chore: updating version for 10.3.0 (#22566)
f902b96 chore: Adding record key context for internal ui jobs (#22559)
54e31e3 chore: Improve pkg/driver types part 2 (#21610)
c0ea9bd fix: use posix path for ts-node loader (#22550)
5d5574e fix: add baseUrl to TestConfigOverrid...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
ornate vigilBOT
ornate vigilBOT
vivid lintelBOT
#

Bumps github.com/stretchr/testify from 1.7.4 to 1.8.0.

Commits

181cea6 impr: CallerInfo should print full paths to the terminal (#1201)
cf1284f Allow mock expectations to be ordered (#1106)
66eef0e fix: assert.MapSubset (or just support maps in assert.Subset) (#1178)
2fab6df Add WithinTimeRange method (#1188)
b5ce165 fixing panic in calls to assertion with nil m.mutex (#1212)
c206b2e Mock can be deadlocked by a panic (#1157)
1b73601 suite: correctly se...

vivid lintelBOT
#

What is the issue?

$ go install github.com/dagger/dagger@latest
go: downloading github.com/dagger/dagger v0.2.21
go: github.com/dagger/dagger@latest (in github.com/dagger/dagger@v0.2.21):
        The go.mod file for the module providing named packages contains one or
        more replace directives. It must not contain directives that would cause
        it to be interpreted differently than if it were the main module.

Log output

No response

Steps to reproduce...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

What are you trying to do?

When I use core.#Source for a node project, I only want to include files that are actually tracked in git. Conveniently, we already have files that tell git what to ignore ie. .gitignore. It would be nice if we had 2 things:

  1. Recursive exclude - Currently, excluding "node_modules" only excludes the top level folder, but not any in subfolders
  2. The ability to reference a file with a list of files to exclude. In this case, .gitignore.

I apologize ...

vivid lintelBOT
#

Since your test in test/image.cue has package codecov at the top, and you're in the codecov package directory tree, you don't need to import the universe.dagger.io/alpha/codecov package and don't need to use codecov.#Image just #Image. Like this:

package codecov

import (
	"dagger.io/dagger"
)

dagger.#Plan & {
	actions: test: #Image & {}
}

Comment from user:

How does it handle ambiguous package names in different paths? My gut tells me staying explicit is generall...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Bumps clsx from 1.1.1 to 1.2.0.

Release notes
Sourced from clsx's releases.

v1.2.0
Features

Add named clsx export alias (#43, #44): 56ab81f
Thank you @โ€‹danikaze~!
This is purely an alias for the default export so that TypeScript users can avoid the esModuleInterop setting. In other words, the follow import statements are effectively identical, but the latter is preferred by TypeScript:
import clsx from 'clsx';
// or
import { clsx } from 'clsx';

Importan...

vivid lintelBOT
vivid lintelBOT
ornate vigilBOT
#

I just came accross dagger today and have a few questions. I would really appreciate some guidance whether dagger is what I am looking for, which I hope :breites_lรคcheln:
Currently, we are in the process of changing to a Python monorepo where we will use https://www.pantsbuild.org/ as the build system (we will have to rewrite CI/CD as well then). It is a great tool for packaging our application build artifacts from the monorepo. It also supports building docker images, but I am having the fe...

ornate vigilBOT
#

In the past couple months I've created a few Dagger actions, some of them behave a bit differently (by default) when running in a local environment compared to CI or when running them on PRs compared to tags.

Typically, publishing steps should "dry run" by default in a local environment / non-tag CI runs.

So far I used the following style:

package main

dagger.#Plan & {
	client: filesystem: ".": read: _
	client: env: {
		CI: string | *""
	}
	actions: {
		someAction: m...
#

Seems to me the current convention is what you're already doing. I.e., do a field comprehension based on an env var's value or something similar.

If you mean that you wish your action had access to the client's env vars without having to pass through from client, you're not the first to ask (#2437).

If not, do you have an idea of something else that would be much better?

You can also group actions such that you can do dagger do ci someAction vs dagger do someAction on the diffe...

ornate vigilBOT
#

I don't necessarily have a better idea (yet), I wanted to start a conversation about the topic and see what other people do.

Having access to client env vars from actions would be nice, but I also get why it's not implemented that way.

You can also group actions

I thought about that, but it feels a bit weird. Ideally, I'd want my pipelines to be portable across environments and user env vars/parameters to configure pipelines. Having completely different groups is like having differ...

#

It looks like most of your problem can be summarized as: orchestrating docker builds, which dagger can handle pretty easily. Before I dig into your points below, I'd recommend reading those 2 guides from the dagger doc:

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

GoReleaser v1.10 update broke our releases: https://github.com/dagger/dagger/runs/7205381884?check_suite_focus=true#step:8:116

It tried building a windows_arm64 version which is not possible with Go 1.16. This has more details: https://github.com/goreleaser/goreleaser/issues/3224

Instead of pinning to GoReleaser v1.9.2 (last version that worked https://github.com/dagger/dagger/runs/7097754532?check_suite_focus=true#step:8:15) we should do the right thing and bump the Go version that w...

vivid lintelBOT
vivid lintelBOT
ornate vigilBOT
#

I think portability and reproducability will be a great enhancement in terms of CI/CD with dagger. I can test those pipelines locally and be sure they run on CI. And for the specific case of orchestrating docker builds for all the microservices it can be considered very helpful.

I am a little worried about two things:

  1. Maintaining some wrapper around pants, i.e. through a dagger package. I have not thought about it in depth, but I would like to remain access to all pants commands
  2. ...
vivid lintelBOT
vivid lintelBOT
#

Bumps clsx from 1.2.0 to 1.2.1.

Release notes
Sourced from clsx's releases.

v1.2.1
Patches

Ensure CommonJS and UMD entrypoints have the named clsx export too

Chores

Build CJS & UMD files manually (#50): 3712966, 2114f5b

Full Changelog: https://github.com/lukeed/clsx/compare/v1.2.0...v1.2.1

Commits

6da37d6 1.2.1
62d6071 chore: revert version bump
2114f5b chore(bin): mkdir if missing
3712966 chore: build CJS & UMD files manually;
See full d...

vivid lintelBOT
vivid lintelBOT
#

PR #2748 added support for HTTP and HTTPS proxy from environment variables inside actions tasks. However it actually supports proxies for anything using core.#Exec. The proxy env vars will be ignored for other ops involving network connections: core.#GitPull, core.#HTTPFetch, core.#Pull.

It's not critical as most packages are built on top of core.#Exec. Also, not sure if there is a proper way to support proxies outside of a llb Exec.

Related issues: #2053 #1369

cc @dolanor...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
ornate vigilBOT
#

Personally, I'd keep a final gate in the form of manual approve from a maintainer before promoting something to prod.

There is also the question of versioning (or backward compatibility promise). Since everything is in a single, giant repo it seems quite hard to do versioning. So anything that gets promoted to prod (or even beta) needs to stay backward compatible....indefinitely? At the very least we need to specify the requirements around backward compatibility.

After writing a couple ...

ornate vigilBOT
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Bumps go.opentelemetry.io/otel/sdk from 1.4.1 to 1.8.0.

Release notes
Sourced from go.opentelemetry.io/otel/sdk's releases.

Release v1.6.3
Fixed

Allow non-comparable global MeterProvider, TracerProvider, and TextMapPropagator types to be set. (#2772, #2773)

Release v1.6.2
1.6.2 - 2022-04-06
Changed

Don't panic anymore when setting a global TracerProvider or TextMapPropagator to itself. (#2749)
Upgrade go.opentelemetry.io/proto/otlp in...

#

Bumps go.opentelemetry.io/otel/exporters/jaeger from 1.4.1 to 1.8.0.

Release notes
Sourced from go.opentelemetry.io/otel/exporters/jaeger's releases.

Release v1.6.3
Fixed

Allow non-comparable global MeterProvider, TracerProvider, and TextMapPropagator types to be set. (#2772, #2773)

Release v1.6.2
1.6.2 - 2022-04-06
Changed

Don't panic anymore when setting a global TracerProvider or TextMapPropagator to itself. (#2749)
Upgrade go.open...

#

Bumps go.opentelemetry.io/otel/trace from 1.4.1 to 1.8.0.

Release notes
Sourced from go.opentelemetry.io/otel/trace's releases.

Release v1.6.3
Fixed

Allow non-comparable global MeterProvider, TracerProvider, and TextMapPropagator types to be set. (#2772, #2773)

Release v1.6.2
1.6.2 - 2022-04-06
Changed

Don't panic anymore when setting a global TracerProvider or TextMapPropagator to itself. (#2749)
Upgrade go.opentelemetry.io/proto/otl...

#

Bumps go.opentelemetry.io/otel from 1.4.1 to 1.8.0.

Release notes
Sourced from go.opentelemetry.io/otel's releases.

Release v1.6.3
Fixed

Allow non-comparable global MeterProvider, TracerProvider, and TextMapPropagator types to be set. (#2772, #2773)

Release v1.6.2
1.6.2 - 2022-04-06
Changed

Don't panic anymore when setting a global TracerProvider or TextMapPropagator to itself. (#2749)
Upgrade go.opentelemetry.io/proto/otlp in go.open...

vivid lintelBOT
#

Bumps @docusaurus/core from 2.0.0-beta.21 to 2.0.0-beta.22.

Release notes
Sourced from @โ€‹docusaurus/core's releases.

2.0.0-beta.22 (2022-07-08)
:boom: Breaking Change

docusaurus-theme-classic

#7740 refactor(theme): nest theme icons under subfolder @โ€‹theme/Icon/* (@โ€‹slorber)

docusaurus-plugin-content-blog, docusaurus-theme-classic, docusaurus-theme-common

#7716 refactor(theme): split BlogPostItem into smaller theme ...

vivid lintelBOT
#

Before this commit, if user has an invalid Dagger plan and runs dagger do without any arguments, they'll get an error and the execution won't
be uploaded to Dagger Cloud. This allows uploading the user's plan
even though it's invalid.

This change will very likely help new users trying to create plans
without too much knowledge of the dagger CUE specific definitions.

Signed-off-by: Marcos Lilljedahl

vivid lintelBOT
vivid lintelBOT
#

Notes:

  • Creation of cue.mod/usr during init was removed for simplification
  • Removed concept of "root" module because the distinction is only useful in some advanced cases
  • Changed foo/bar references to example.com except for the final "Practice" examples. I feel foobar is more ok in tests but not in docs. I'd like a more realistic (albeit simple) example in the end, but left mostly as is for now.
  • Changed #Foo action to use action outputs as the result is much cleaner than looki...
vivid lintelBOT
#

What are you trying to do?

Sometimes you want to push an image to multiple tags (e.g., 0.1.0 and latest). BuildKit supports this by setting name to multiple values split by a comma:

push: core.#Push & {
	dest:  "localhost:5042/test1:\(randomString.output),localhost:5042/test1:latest,localhost:5042/test1:random"
	input: randomString.image.output
	config: env: FOO: randomString.output
}

Full plan

package main

import (
	"dagger.io/dagger"
	"dagge...
vivid lintelBOT
vivid lintelBOT
#

Problem

We want to protect the user from trying to nest core actions since they'll be ignored for execution. As described in the following issue, the core.#Stop and core.#SendSignal core actions reference core.#Start as a valid use case here:

Solution

Refactor out this pattern to avoid referencing another core action directly. Most likely using a field from it instead.

TODO: design proposal

#

Resolves #2303

Overview

Nested core actions are ignored in cue/flow, but still can be used for forcing dependencies with other core actions.

If we want to protect the user against a mistake, we must also change this forced dependency pattern to use a field instead of the core action itself.

Error example

From running the tests/plan/validate/nested/nested.cue test:

actions.test.shallow: found nested core action: actions.test.shallow._write:
    ./tests/p...
vivid lintelBOT
vivid lintelBOT
ornate vigilBOT
#

While integrating various tools into Dagger plans, several patterns emerged to allow users the customization of base images/tool versions. While one isn't necessarily better than the other, there should be some guidelines for which patterns to use in Universe to make maintenance easier.

The patterns I've seen so far:

  • No specific API, users can change the container image of an action through input
  • Definition accepts a version parameter that downloads a default image, otherwise u...
vivid lintelBOT
#

Dagger Cloud run URL

https://dagger.cloud/runs/ab98d285-7037-48db-8491-0f157049e291

What happened? What did you expect to happen?

The core.#CacheDir seem to not store the modification done from the container. It can be reproduced by running dagger do test multiple times and observe the "./export/ls" which should be appended from result of each execution but instead the content is replaced each time the dagger do is executed. Unless i'm mistaking the way core.#CacheDir works, si...

ornate vigilBOT
#

If you used https://dagger.cloud with dagger let us know what worked well and what you wish was better. All & any feedback welcome!

If you are curious to learn more about how Dagger Cloud makes debugging dagger issues easier, this doc page explains how to get started: Debugging with Dagger Cloud.


@mircubed @marcosnils please edit this as you see fit (maybe starting with this comment). I just needed a link to...

vivid lintelBOT
ornate vigilBOT
#

I was using Dagger Cloud yesterday and noticed a few issues:

vivid lintelBOT
#

What are you trying to do?

When people see the CUE code, [some (myself and some other daggernaut as well)](#help-old-do-not-post message) try to actually access that URL.
Except for now, there is no service running at that address.

Why is this important to you?

It would be great if we could host some documentation server at that URL, so people could actually explore what there is in this package. It would improve self explora...

ornate vigilBOT
#

Hi ๐Ÿ‘‹๐Ÿป

First, a firm handshake to the team behind Dagger, you're doing a great job easing our CI's ๐Ÿ˜…

This discussion is focused on how Dagger works and how it may be adapted to specific needs, I've been through the documentation and the API (both dagger.io and universe.dagger.io) and I didn't found anything about using Dagger as an orchestrator on top of tools like Makefile / Taskfile, did I miss something?

Here's the use case I'm facing:

  • The project use Docker / Dock...
ornate vigilBOT
ornate vigilBOT
ornate vigilBOT
#

cc @slumbering UI feedback

yes, this is because there's no current JS cue highlighter. We have discussed about this and we're looking for alternatives.

  • showing logs in full-screen, [similar to how Papertrail used to do i...
vivid lintelBOT
#

What is the issue?

When you pass a decoded secret to a dagger.#Secret field, the validator panics.

Essentially this:

token: dagger.#Secret & decode.output.apiToken.contents

When checking for core types, we need to do it only if it's a struct:

	// Core types (FS, Secret, Socket): make sure they are references, otherwise abort.
	case plancontext.IsFSValue(v) || plancontext.IsSecretValue(v) || plancontext.IsSocketValue(v):

As a workaround for now t...

ornate vigilBOT
vivid lintelBOT
#

What are you trying to do?

I have a fairly complex plan with nested actions. dagger do --help is great, but a user has to run it multiple times to get a full view of the available actions.

https://github.com/dagger/dagger/blob/95c418101d008d46737850aa20d6181f853458b1/cmd/dagger/cmd/doc.go#L372-L380

Why is this important to you?

It would be a helpful feature for users who aren't familiar with the dagger plan to have one command that provides an aggregate view of all of the act...

ornate vigilBOT
vivid lintelBOT
#

What are you trying to do?

In a dagger plan, if you include two Yarn actions and you don't specify a project field (which is optional), that will cause undesired effect in caching since both actions will share the same cache id as the project field is used here https://github.com/dagger/dagger/blob/main/pkg/universe.dagger.io/yarn/yarn.cue#L134 and here https://github.com/dagger/dagger/blob/main/pkg/universe.dagger.io/yarn/yarn.cue#L141 respectively.

An evident proposal to ...

#

Bumps google.golang.org/grpc from 1.47.0 to 1.48.0.

Release notes
Sourced from google.golang.org/grpc's releases.

Release 1.48.0
Bug Fixes

xds/priority: fix bug that could prevent higher priorities from receiving config updates (#5417)
RLS load balancer: don't propagate the status code returned on control plane RPCs to data plane RPCs (#5400)

New Features

stats: add support for multiple stats handlers in a single client or server (#5347)
gcp/observabili...

ornate vigilBOT
ornate vigilBOT
#

You're right, there's several patterns that have emerged and we need a consensus.

The way I see it, we should move away from having a default image inside main actions.

Two reasons:

  1. Can't stack default values if you want to create a higher abstraction on top;
  2. Even if you override with your own custom image, the default one is still being evaluated and executed, which is wasteful.

Here's my recommendations for conventions...

Default package image to cover most c...

ornate vigilBOT
#

This seems like a complicated area, especially the default images. I had to read it five (5) times to start understanding it. I can see this getting others too, like @rawkode in this context: #help-old-do-not-post message (thanks for the connection @helderco). Pretty sure this will continue coming up until we clarify a few things. Leaving it at this for now.

Once again, thank you @sagikazarmark for kicking this off โšฝ๏ธ

vivid lintelBOT
#

This is similar to https://github.com/dagger/dagger/pull/2766, but with a GHA cache fix. Integration tests pass consistently locally, on Linux, but fail consistently on GitHub Actions. My only explanation is the GitHub Actions cache. This is the follow-up to this comment: https://github.com/dagger/dagger/pull/2766#issuecomment-1183851791

FWIW, I expect integration tests to fail for this commit, same as https://github.com/dagger/dagger/runs/7331502142?check_suite_focus=true

ornate vigilBOT
ornate vigilBOT
#

Would you create a "simple" variant with a default image?

Yes.

  1. there should be a version without a default image, where you're required to provide during usage
  2. there should be an image definition, e.g., golangci.#Image, to easily use it above for the more most common case
  3. there should be a variation of the action where the package's #Image is already set up for convenience

Each point builds upon the last, from flexibility to simplified usage.

What I'm ...

vivid lintelBOT
#

Bumps @docusaurus/core from 2.0.0-beta.22 to 2.0.0-rc.1.

Release notes
Sourced from @โ€‹docusaurus/core's releases.

2.0.0-rc.1 (2022-07-14)
:bug: Bug Fix

docusaurus

#7776 fix(core): swizzle --eject js should not copy theme .d.ts files (@โ€‹slorber)
#7750 fix(deploy): revert "feat(deploy): copy local git config to tmp repo (#7702)" (@โ€‹ghostsquad)

docusaurus-plugin-sitemap

#7774 fix(sitemap): complete gracefull...

ornate vigilBOT
#

The way I see it, docker.#Run expects an image as an input parameter by definition, whereas you wouldn't pass a container image to a lint command, so they are somewhat different.

From a consumer perspective, the API provided by these CUE packages let me run and parametrize the tools I wanted to use. The fact that I need to run them as container images is kind of an implementation detail. So if we are looking for a driving force for API design decisions, I would approach from this directi...

ornate vigilBOT
#

Yes, that's it. And I like the word "Base" much better ๐Ÿ™‚

You wouldn't pass a container image to a lint command, but golangci.#Lint does have it's own internal image, which you may need to customize for some reason:

	_image: docker.#Pull & {
		source: "index.docker.io/golangci/golangci-lint:v\(version)"
	}

So in that sense, it's the same thing, except in this case it's not a default, it's hardcoded. What really matters is the **presence of a default sub-action that c...

#

Yes, that's it. And I like the word "Base" much better ๐Ÿ™‚

You wouldn't pass a container image to a lint command, but golangci.#Lint does have it's own internal image, which you may need to customize for some reason:

	_image: docker.#Pull & {
		source: "index.docker.io/golangci/golangci-lint:v\(version)"
	}

So in that sense, it's the same thing, except in this case it's not a default, it's hardcoded. What really matters is the **presence of a default sub-action that c...

vivid lintelBOT
#

The problem with bash.#Run is that if the user provides an image without bash, it fails. This is fine, until you consider the use-case of yarn.#Script, which uses bash.#Run internally and it's a pain to use a custom image with recent versions of node, as you need to inject it into the yarn.#Run.input and yarn.#Run.install.container.input.

Now, this could be a design issue with yarn.#Run and I could have added the shell override to bash.#Run quite easily - but then it wouldn't...

vivid lintelBOT
vivid lintelBOT
#

Rather than using first version of CUE - head -1 - from go.mod, we want to use the last version - tail -n 1. While I am not sure why we have two versions of CUE in the go.mod, based on various internal discussions, I do know that there are various edge case issues with CUE > 0.4.1. With the current progress that upstream contributions are making, we continue being stuck with 0.4.1 for now. Related to:

vivid lintelBOT
#

What is the issue?

There's an edge case during plan validation where IsReference() is returning false.

// doesn't work
actions: test: #Foo & {
	bar: #Bar
}
#Foo: {
	bar: #Bar
}

This should be the same as:

// works
actions: test: #Foo

#Foo: {
	bar: #Bar & #Bar
}

In this case, validation is failing on this field from docker.#Run:

export: rootfs: dagger.#FS & _exec.output

v.ReferencePath() returns an empty value.

Log ...

vivid lintelBOT
vivid lintelBOT
#

What are you trying to do?

Users onboarding on Dagger sometimes need to login to their docker account in order to avoid triggering the rate limiting pull issues on the docker hub. However, most of our packages don't easily enable that.

Issue based on comments: https://github.com/dagger/dagger/issues/2238#issuecomment-1183530615

Solution:

The way @helderco  suggested it was just to have two settings (e.g., DOCKERHUB_AUTH_USER, DOCKERHUB_AUTH_PASS) to apply in Go if they exist...
vivid lintelBOT
#

What are you trying to do?

I want to add a new helm action, helm.#Upgrade which is more useful than install in pipelines that run often. Additionally, this action should have more options to control the deployment, such as setting flags and values.

The usage could look something like this:

release: helm.#Upgrade & {
  kubeconfig: client.commands.kubeconfig.stdout
  workspace:  client.filesystem.".".read.contents
  name:       "vault"
  repo:       "https://helm.releases...
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Fixes issue #2802.

Transforms the export key of docker.#Run from rootfs: dagger.#FS & _exec.output to rootfs: _exec.output.

The previous unification made Cue not return any selector for the given expression.

To give more context, the below plan, with or without the first bar key commented, retrieves the same refPath. However, one has Selectors, the other is nil:

dagger.#Plan & {
	actions: test: #Foo & {
		// commenting this line fixes the error
		bar: #Bar
...
vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

What is the issue?

We advise users to generally avoid raw strings here: https://docs.dagger.io/1226/coding-style/#avoid-raw-strings

but they are needed when doing shell style line continuation such as

dockerfile: contents: """
    FROM ubuntu:18.04 as PHP
    ENV DEBIAN_FRONTEND noninteractive

    RUN apt-get update && apt-get install -y \
    nano \
    ....

where the above throws an error
ERROR system | failed to load plan: unknown escape sequence:

the err...

vivid lintelBOT
vivid lintelBOT
vivid lintelBOT
#

Bumps github.com/sirupsen/logrus from 1.8.1 to 1.9.0.

Commits

f8bf765 Merge pull request #1343 from sirupsen/dbd-upd-dep
ebc9029 update dependencies
56c843c Merge pull request #1337 from izhakmo/fix-cve
41b4ee6 update gopkg.in/yaml.v3 to v3.0.1
f98ed3e Merge pull request #1333 from nathanejohnson/bumpxsys
2b8f60a bump version of golangci-lint
0db10ef bump version of golang.org/x/sys dependency
85981c0 Merge pull request #1263 from rubensayshi/fix-race
7...

#

Bumps cypress from 10.3.0 to 10.3.1.

Release notes
Sourced from cypress's releases.

v10.3.1
Changelog: https://docs.cypress.io/guides/references/changelog#10-3-1

Commits

ae4a9d8 10.3.1 release
1da95a7 fix: Determine global mode based on whether there is a current project (#22838)
2aa7b93 fix: Correct pluralization in Spec Pattern (#22773)
89acf9c chore: add types to screenshots (#22768)
0aebe4a trigger build for 10.3.1
1643161 fix: show info mess...

#

Bumps @svgr/webpack from 6.2.1 to 6.3.0.

Release notes
Sourced from @โ€‹svgr/webpack's releases.

v6.3.0
Bug Fixes

core: types field in package.json (#693) (a491ace)
package.json: fix exports (#745) (2a368d1)

Features

add descProp option (#729) (a0637d4)
cli: output file name when error happen to handling a file (#702) (0ec1fbd)

Changelog
Sourced from @โ€‹svgr/webpack's changelog.

6.3.0 (2022-07-18)
Bug Fixes

core: types field in package.json (#693) ...

#

Bumps concurrently from 7.2.2 to 7.3.0.

Release notes
Sourced from concurrently's releases.

v7.3.0
What's Changed

Export package.json path by @โ€‹gustavohenke in open-cli-tools/concurrently#339

Commits

1220aeb 7.3.0
f94b456 Export package.json path (#339)
30ffed0 Use full link for license badge
df632df Update description of the badges
c6c5409 Replaces badges in README
02b9082 Enhance tests (#335)
cc05702 Switch to new CI badge
39beb72 Fi...

vivid lintelBOT
vivid lintelBOT
#

Bumps terser from 5.10.0 to 5.14.2.

Changelog
Sourced from terser's changelog.

v5.14.2

Security fix for RegExps that should not be evaluated (regexp DDOS)
Source maps improvements (#1211)
Performance improvements in long property access evaluation (#1213)

v5.14.1

keep_numbers option added to TypeScript defs (#1208)
Fixed parsing of nested template strings (#1204)

v5.14.0

Switched to @โ€‹jridgewell/source-map for sourcemap generation (#1190, #1181)
Fixe...

vivid lintelBOT
vivid lintelBOT
#

Bumps go.opentelemetry.io/otel/trace from 1.4.1 to 1.8.0.

Release notes
Sourced from go.opentelemetry.io/otel/trace's releases.

Release v1.6.3
Fixed

Allow non-comparable global MeterProvider, TracerProvider, and TextMapPropagator types to be set. (#2772, #2773)

Release v1.6.2
1.6.2 - 2022-04-06
Changed

Don't panic anymore when setting a global TracerProvider or TextMapPropagator to itself. (#2749)
Upgrade go.opentelemetry.io/proto/otl...

#

Bumps go.opentelemetry.io/otel from 1.4.1 to 1.8.0.

Release notes
Sourced from go.opentelemetry.io/otel's releases.

Release v1.6.3
Fixed

Allow non-comparable global MeterProvider, TracerProvider, and TextMapPropagator types to be set. (#2772, #2773)

Release v1.6.2
1.6.2 - 2022-04-06
Changed

Don't panic anymore when setting a global TracerProvider or TextMapPropagator to itself. (#2749)
Upgrade go.opentelemetry.io/proto/otlp in go.open...

vivid lintelBOT
ornate vigilBOT
#

This one is important for my organization. Also, TeamCity supports inheritance, while Jenkins and others do not.

Example: root project (with secrets to access git and triggers for pull request) has a child of build artifacts, which builds binaries on various platforms, and this has test children pipelines for integration tests and unit tests that consume the artifacts, so root > build > {unit_tests, integration_tests}.

, so for example, integration test pipeline and unit test p...

ornate vigilBOT
#

I am interested in Spinnaker CD pipelines, which are reflected in JSON, and can be downloaded. They can also be uploaded with changes to create new pipelines. There's a CLI tool that I use to manage the pipelines https://spinnaker.io/docs/guides/spin/pipeline/

Sounds like an ideal use for Dagger. You could consume/generate the Spinnaker JSON and invoke the CLI. Let me know if you'd like to set up a POC/pilot to get that going :)

vivid lintelBOT
vivid lintelBOT