status stringclasses 1
value | repo_name stringclasses 13
values | repo_url stringclasses 13
values | issue_id int64 1 104k | updated_files stringlengths 11 1.76k | title stringlengths 4 369 | body stringlengths 0 254k ⌀ | issue_url stringlengths 38 55 | pull_url stringlengths 38 53 | before_fix_sha stringlengths 40 40 | after_fix_sha stringlengths 40 40 | report_datetime timestamp[ns, tz=UTC] | language stringclasses 5
values | commit_datetime timestamp[us, tz=UTC] |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
closed | dagger/dagger | https://github.com/dagger/dagger | 1,352 | ["website/package.json", "website/yarn.lock"] | Europa: add formatting constraints to `engine.#Ref` | New Europa API defines `#Ref` type for docker image ref. Currently it’s a simple string, but could be restricted further as a convenience to developers.
| https://github.com/dagger/dagger/issues/1352 | https://github.com/dagger/dagger/pull/640 | 06f04be21438daf02780389a2a2aa1aa871eb6b6 | 53fa2844c0fac588b5742bd66e8a115c50e3160b | 2022-01-06T20:02:10Z | go | 2021-06-15T12:27:23Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,344 | ["cmd/dagger/cmd/mod/get.go", "mod/repo.go", "pkg/pkg.go"] | mod get doesn't work in Europa | Since it relies on "projects" (e.g. `.dagger`), `mod get` doesn't work anymore. | https://github.com/dagger/dagger/issues/1344 | https://github.com/dagger/dagger/pull/1519 | f47d44da79db91905cf7851061087b7231ec0260 | 7b8a637bea7039e2433783b1a2a97c495920beec | 2022-01-06T01:39:51Z | go | 2022-01-28T17:39:25Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,339 | ["pkg/dagger.io/dagger/engine/image.cue", "pkg/universe.dagger.io/docker/set.cue", "pkg/universe.dagger.io/docker/test/docker.bats", "pkg/universe.dagger.io/docker/test/set.cue"] | Europa: Set image metadata in a Docker build | ## Problem
The new Docker Build API in Europa (`universe.dagger.io/docker.#Build`) lacks the ability to set Docker image metadata. As compared to Dockerfile features:
| Feature | Dockerfile operation | CUE operation |
| -- | -- | -- |
| Set default working directory | `WORKDIR <PATH>` | Not available |
| Set d... | https://github.com/dagger/dagger/issues/1339 | https://github.com/dagger/dagger/pull/1535 | 946629d1faf7e32f3e1ba535dad762886bbe5b41 | 676a895a0f33dad5c5f3330716ac12942cd351aa | 2022-01-04T22:51:06Z | go | 2022-02-01T00:09:22Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,305 | ["client/client.go", "docs/reference/europa/dagger/engine.md", "plan/task/newsecret.go", "stdlib/europa/dagger/engine/secret.cue", "tests/tasks.bats", "tests/tasks/newsecret/newsecret.cue"] | Support loading secrets from actions | It's currently not possible to load new secrets from a plan -- secrets can only be passed as inputs.
This led to secrets-generating packages to output `string`s instead, and have other packages arbitrarily support either strings or secrets which is messy.
Proposal: `engine.#NewSecret` task with pretty much the sa... | https://github.com/dagger/dagger/issues/1305 | https://github.com/dagger/dagger/pull/1307 | 4dec90a9624582ba0696e4cabff4357adcc40d11 | c5126412b0f5543590185d606a944d37a65ffaa2 | 2021-12-23T16:14:11Z | go | 2022-01-10T20:09:21Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,287 | ["core/docs/d7yxc-operator_manual.md", "docs/current/faq.md"] | support rootless mode? | One of the install steps here shows how to use 'sudo' to install it: https://docs.dagger.io/1001/install/
That shouldn't be needed, lately I use containers that run in rootless mode (e.g. `podman` instead of `docker` and a wrapper that calls `podman` instead of `docker` for backwards compat, or `runc`, etc.), and a ro... | https://github.com/dagger/dagger/issues/1287 | https://github.com/dagger/dagger/pull/5809 | 8f6c3125f14a31e39e251492897c86768147fe26 | e63200db6dd4da2ceff56447d99b01056140b482 | 2021-12-22T00:16:02Z | go | 2023-10-12T22:04:22Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,256 | ["go.mod", "go.sum", "plan/plan.go", "tests/tasks/hidden/cue.mod/module.cue", "tests/tasks/hidden/cue.mod/pkg/.gitignore", "tests/tasks/hidden/cue.mod/usr/testing.dagger.io/hidden/hidden.cue", "tests/tasks/hidden/hidden.cue"] | Europa: actions in hidden fields | ## Problem
There may or may not be a problem, depending on whether the desired behavior is already supported.
## Desired behavior
Dagger should support configuring actions in hidden fields. For example:
```
// Action configured in a regular field
foo: docker.#Run & {
script: “echo hello foo!”
}
// ... | https://github.com/dagger/dagger/issues/1256 | https://github.com/dagger/dagger/pull/1403 | f13c0fe1d8bd246ce4b690cc2c9c30cd96b7bb5c | 9b81b46677eac098713927106bad74d1434a3c52 | 2021-12-17T19:57:39Z | go | 2022-01-12T20:42:46Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,249 | ["go.mod", "go.sum"] | Terminate an action | ## Problem
Dagger has the ability to run commands in containers (`engine.#Exec`). These commands can be long-running (for example a test database). But there is no reliable way to terminate this command later. This effectively makes it impossible to execute long-running commands without hanging DAG execution.
A t... | https://github.com/dagger/dagger/issues/1249 | https://github.com/dagger/dagger/pull/781 | 696b8a4d4cb8831c8c316dbe15e94bbbaa9d9fb2 | 58eebc5f8d9af0dbd838815151b9c7318afdc802 | 2021-12-17T07:12:18Z | go | 2021-07-03T16:22:32Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,222 | ["europa-universe/docker/docker.cue", "stdlib/europa/dagger/engine/spec/engine/exec.cue"] | Europa: engine.#Exec: attach stdin, stdout, stderr | Expand the Engine API to give developers control over the standard streams (stdin, stdout, stderr) of the commands they’re executing.
This was part in the original Europa spec, but was temporarily removed to resolve outstanding design issues:
* How to handle multiple writers? Are they forbidden? Do they randomly ... | https://github.com/dagger/dagger/issues/1222 | https://github.com/dagger/dagger/pull/1223 | 19322a7cb9c58866661f4eae31bf3f37722d366d | 9e859e6233374b2c611b1db366e22cf737eae174 | 2021-12-14T22:27:52Z | go | 2021-12-17T01:17:38Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,220 | ["cmd/dagger/cmd/up.go", "plan/plan.go"] | Europa: Stopgap implementation to output computed state | In Europa we're missing a way to retrieve state (e.g. `dagger query`).
I don't know what the long term solution would look like, and maybe we don't need to figure that out for the Europa release.
However, in the meantime, we do need **some** way to programmatically get the computed state back, at the very least f... | https://github.com/dagger/dagger/issues/1220 | https://github.com/dagger/dagger/pull/1279 | cbd141d019d48e839d6b647923f9563a2c2b09a6 | f3caa342e8721541a5aa32a0020fd5d8b52d646f | 2021-12-14T14:57:19Z | go | 2021-12-21T17:48:04Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,218 | ["docs/learn/1011-package-manager.md"] | docs: 404 to github.com/dagger/packages | Issue inside https://docs.dagger.io/1011/package-manager/#install
GitHub link send to `https://github.com/dagger/packages/blob/main/gcpcloudrun/source.cue`
and returns to a 404 (private repo maybe?).
| https://github.com/dagger/dagger/issues/1218 | https://github.com/dagger/dagger/pull/1428 | 971346c6d57ba8283cfc486e8bd11273165f38e6 | 63d655d8f39f08ecc0cd56baed7ff354efbb3ba9 | 2021-12-14T10:33:21Z | go | 2022-01-14T08:30:47Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,207 | ["go.mod", "go.sum"] | Hidden fields traversal for cue/flow | We should support `_hidden` tasks in Europa.
This requires upstream support, for which @jlongtine already opened a PR: https://github.com/cue-lang/cue/pull/1419 | https://github.com/dagger/dagger/issues/1207 | https://github.com/dagger/dagger/pull/2698 | bbfef122d98226003da8930117abf66fae61c829 | 16c6675f1353da8d96aab19e40f9a0dcc7b98fd4 | 2021-12-13T15:20:07Z | go | 2022-06-23T08:29:14Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,205 | ["cmd/dagger/cmd/common/track.go", "telemetry/telemetry.go"] | Include CI runners in analytics | Currently `dagger` sends basic analytics on long-running commands (this can be disabled with the semi-standard DO_NOT_TRACK environment variable). But not all commands are included in the analytics: commands run in a CI environment (according to best-effort heuristics) are entirely skipped. This results in an analytics... | https://github.com/dagger/dagger/issues/1205 | https://github.com/dagger/dagger/pull/1801 | a406b15ef403ca55bbac98807b151b763fab2029 | e9d3b2fd15569e9b4ae66c2504d4c8439a810077 | 2021-12-11T03:26:40Z | go | 2022-03-14T23:11:26Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,159 | ["website/yarn.lock"] | Document dagger auto-completion | Thanks to viper, dagger supports shell auto-completion natively:
e.g.: `dagger completion zsh`
We should document it as it's a very low hanging fruit to improve the UX. | https://github.com/dagger/dagger/issues/1159 | https://github.com/dagger/dagger/pull/2822 | 59adcef42f8d085335dac015715a96872ea78c18 | db172bf3bdafbf4f99fd9fec7d617fac793fb400 | 2021-11-23T19:44:54Z | go | 2022-07-21T08:06:46Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,118 | ["cmd/dagger/cmd/up.go", "mod/mod.go"] | Broken dagger init | This is multiple problems, very possibly related, found by @kzap while following the getting started tutorial.
### Problem #1: no secret keys
For some reason, the `keys.txt` file was corrupted (missing the key information):
```
$ dagger new local -p ./plans/local
9:16PM FTL system | failed to create environ... | https://github.com/dagger/dagger/issues/1118 | https://github.com/dagger/dagger/pull/1196 | 9b2746b2cb1e75bb8143b114527b4673a42aa598 | bbc938ddd6cf9035e3170c8a7679a3a47846eed0 | 2021-11-10T02:52:01Z | go | 2021-12-21T16:58:17Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,111 | ["Makefile", "cmd/dagger/cmd/input/socket.go", "environment/pipeline.go", "go.mod", "go.sum", "solver/socketprovider.go", "solver/socketprovider_unix.go", "solver/socketprovider_windows.go", "state/input.go", "stdlib/dagger/dagger.cue"] | Support `input stream` on Windows | Currently, most examples work out of the box on Windows, unless the config requires access to the local docker socket (eg. "Getting started" from the docs).
We need to implement npipe support for Windows so the client can proxy `\\.\pipe\docker_engine` (host) to `/var/run/docker.sock` (WSL).
This last change shou... | https://github.com/dagger/dagger/issues/1111 | https://github.com/dagger/dagger/pull/1112 | 2d371ca32b8ecf2569e6b10456be6252360e7cb1 | 8ffee8922eeff3de6b5faf6c4c51c96839890586 | 2021-11-08T23:10:41Z | go | 2021-11-09T02:06:50Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,105 | ["solver/registryauth.go", "solver/registryauth_test.go"] | Target when logging in to a private registry in a build requires a repo? | It appears that when I connect to my private registry for a build, I get an unauthorized response unless the target includes a repo (even if it doesn't exist).
```cue
package main
import (
"alpha.dagger.io/dagger"
"alpha.dagger.io/dagger/op"
)
#Auth: {
target: dagger.#Input & {string}
use... | https://github.com/dagger/dagger/issues/1105 | https://github.com/dagger/dagger/pull/1454 | abcd01ccfa5ffa88669b61af77b59258e5bd795c | 587f92c9243e18ae69ab4373a7f48cfc248afe5d | 2021-11-07T21:00:07Z | go | 2022-01-20T02:16:34Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,087 | ["environment/pipeline.go", "solver/solver.go", "stdlib/universe.bats"] | multi-arch support broke docker.#Push | Follow-up of merging https://github.com/dagger/dagger/pull/1074
On the todoapp example, it gives me this error on push.
<img width="944" alt="Screen Shot 2021-11-01 at 4 16 45 PM" src="https://user-images.githubusercontent.com/216487/139754301-32c429ef-d95e-47b0-9280-8bd0d6372da4.png">
Not sure the root cause ... | https://github.com/dagger/dagger/issues/1087 | https://github.com/dagger/dagger/pull/1089 | 954192118e563dc0b4b8215d5b2c0e7096ae3ab0 | 2cc3f9ad5a47f98181bb239566e9a158e9ff0145 | 2021-11-01T23:23:06Z | go | 2021-11-02T17:58:40Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 1,032 | ["stdlib/git/git.cue", "stdlib/git/tests/git/git.cue"] | Git.#Repository's origin links to a mounted repository, not the provided URL | ### Context
In order to benefit from Buildkit's cache, we are using the `op.#FetchGit` llb instruction to fetch a git repository. However, using this instruction the way we are currently doing, the `origin` ref links a mounted volume, not the URL provided.
### Issue
This is an issue when using git commands using t... | https://github.com/dagger/dagger/issues/1032 | https://github.com/dagger/dagger/pull/1033 | badc3a169da5e02cbe6dec73b4419be8723acb7c | 16d4fc0c98b5af33733cd56ed4bd6b089b8a8fba | 2021-10-04T14:44:07Z | go | 2021-10-04T23:10:20Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 988 | ["go.mod", "go.sum"] | [BUG] Dagger stall when there is no buildkitd active. | When the *dagger-buildkitd* container is not started, the `dagger up` is blocking indefinitely and you have to send SIGTERM signals to stop it.
We should check that the buildkit daemon is active and if not stop the command and print an error stating that the server (or the daemon) is not active or is unavailable. | https://github.com/dagger/dagger/issues/988 | https://github.com/dagger/dagger/pull/4722 | 2ed262c629e4e589d3a335a09dcf8d098fb4848c | 72085322218259ae71cf86cbab51fba08c09da9d | 2021-09-17T14:29:32Z | go | 2023-04-12T16:18:46Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 984 | ["docs/reference/docker/README.md", "stdlib/.dagger/env/docker-run-local/values.yaml", "stdlib/docker/command.cue", "stdlib/docker/compose/compose.cue", "stdlib/docker/docker.cue", "stdlib/docker/tests/run-local/local.cue", "stdlib/universe.bats"] | Enable access to local Docker engine | Accessing a local docker engine in a secure way would be very useful, for onboarding especially.
There is code already merged for this, but not enabled because of unresolved security concerns.
- [x] Implement `dagger.#Stream` primitive to mount a stream into a buildkit container
- [x] Implement a `dagger input s... | https://github.com/dagger/dagger/issues/984 | https://github.com/dagger/dagger/pull/1003 | 9776532fa7cfd933f772bec981ac2fd423887063 | 9120c52545ecb85958efa54ae2adfd1dca731bf3 | 2021-09-15T22:59:14Z | go | 2021-09-23T22:28:26Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 977 | ["go.mod", "go.sum"] | Docs: environment names in tutorials are confusing | Dagger tutorials guide you through the use and creation of various Dagger environments. The names we chose for those environments are confusing users.
Currently the names are:
* [s3](https://docs.dagger.io/1003/get-started/)
* [multibucket](https://docs.dagger.io/1004/dev-first-env/)
* [gcpcloudrun](https://doc... | https://github.com/dagger/dagger/issues/977 | https://github.com/dagger/dagger/pull/1754 | 26fe2630b516dc03995bec7022cb6146f503b437 | 102ec55d4e65b09b153c69b21a984dbcaa5e8f43 | 2021-09-14T20:00:49Z | go | 2022-03-10T19:46:04Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 972 | ["cmd/dagger/cmd/input/dir.go", "tests/cli.bats"] | `dagger input dir src xxxx -e prod` hangs forever | The command `dagger input dir src xxxx -e prod` hangs forever when `xxxx` doesn't exist. | https://github.com/dagger/dagger/issues/972 | https://github.com/dagger/dagger/pull/973 | 4d45e269e006899dc28ba64913a51520aa10a641 | 8dbfdaca1bf2decd474fff5a3ad366fbd3f8eaaf | 2021-09-14T13:58:14Z | go | 2021-09-14T15:44:33Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 941 | ["go.mod", "go.sum"] | Improve display of logs from the CLI during a `dagger up` | Feedback from @benja-M-1
- [x] The part of the logs that are grayed-out are actually very useful and should be highlighted (e.g. Name of the missing input).
- [x] Grouping logs by pipeline (#up) instead of displaying them realtime would be more useful. It's a mess to associate each log line to its corresponding pi... | https://github.com/dagger/dagger/issues/941 | https://github.com/dagger/dagger/pull/4722 | 2ed262c629e4e589d3a335a09dcf8d098fb4848c | 72085322218259ae71cf86cbab51fba08c09da9d | 2021-09-03T00:19:42Z | go | 2023-04-12T16:18:46Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 940 | ["go.mod", "go.sum"] | Support explicit dependency | Sometimes the implicit dependency of the dag is not enough, because a component `A` does not have any useful output for component `B`. However `A` must be executed before `B`.
In such a scenario, it would be useful to have the ability to define a dependency explicitly. | https://github.com/dagger/dagger/issues/940 | https://github.com/dagger/dagger/pull/123 | 9dbec2030cd799ef3d3ba61d4f17d19a3e6f7235 | b1626033dead786076c6f83248a3afcba9e64953 | 2021-09-03T00:10:54Z | go | 2021-02-17T21:28:18Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 905 | ["go.mod", "go.sum"] | Implement ArgoCD | ## Request
Initial [ArgoCD](https://argoproj.github.io/argo-cd/) implementation with app support.
## Requirement
* https://github.com/dagger/dagger/issues/853
## Notes
There is an existing PR (https://github.com/dagger/dagger/pull/883) which will be refactored and moved to a dedicated repository when package... | https://github.com/dagger/dagger/issues/905 | https://github.com/dagger/dagger/pull/1754 | 26fe2630b516dc03995bec7022cb6146f503b437 | 102ec55d4e65b09b153c69b21a984dbcaa5e8f43 | 2021-08-23T08:47:39Z | go | 2022-03-10T19:46:04Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 894 | ["website/package.json", "website/yarn.lock"] | docs.dagger.io search does not work | Any search term entered is blocked on the spinner, see below:
<img width="562" alt="Screen Shot 2021-08-17 at 2 46 01 PM" src="https://user-images.githubusercontent.com/216487/129811283-b2571f10-35fa-4460-a616-fa9f2bc7d4e3.png">
| https://github.com/dagger/dagger/issues/894 | https://github.com/dagger/dagger/pull/5735 | 604fd0e1c4575a9c254b330e6e463ef8094f072e | 9335bcb329a8d43aa351097016d7d57a85bd9852 | 2021-08-17T22:58:17Z | go | 2023-09-13T10:15:02Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 888 | ["cmd/dagger/cmd/input/bool.go", "cmd/dagger/cmd/input/root.go", "state/input.go", "tests/cli.bats", "tests/cli/input/bool/main.cue"] | Bool input type integration (CLI option) | Currently, dagger's CLI doesn't accept a bool type as input:
```shell
➜ universe git:(docs-test) ✗ dagger input
Manage an environment's inputs
Usage:
dagger input [command]
Available Commands:
container Add a container image as input artifact
dir Add a local directory as input artifact
... | https://github.com/dagger/dagger/issues/888 | https://github.com/dagger/dagger/pull/916 | 9d7b40253dc500b1508c741a06bff71384e06f39 | a8b3d9325d5bf794d2928ad0133a9442bd730102 | 2021-08-17T00:48:22Z | go | 2021-08-24T17:51:18Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 884 | ["go.mod", "go.sum"] | Input git doesn't take care of subdir argument | ## Problem
I found an issue with `dagger input git` command.
If we check the usage if input with `dagger input git --help`, here's the result
```
$ dagger input git --help
Add a git repository as input artifact
Usage:
dagger input git TARGET REMOTE [REF] [SUBDIR] [flags]
....
```
We see that we can ad... | https://github.com/dagger/dagger/issues/884 | https://github.com/dagger/dagger/pull/1754 | 26fe2630b516dc03995bec7022cb6146f503b437 | 102ec55d4e65b09b153c69b21a984dbcaa5e8f43 | 2021-08-13T16:34:11Z | go | 2022-03-10T19:46:04Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 856 | ["sdk/nodejs/package.json", "sdk/nodejs/yarn.lock"] | Track all cue performance related PRs [No structure sharing yet] | When developing a bigger use case using Dagger with @TomChv, we encountered performance related problems.
The aim of this issue to regroup all the hacks we will need to implement until Cue's core team fixes the origin of the lag (cf. https://github.com/cue-lang/cue/issues/803)
* All related issues are happening o... | https://github.com/dagger/dagger/issues/856 | https://github.com/dagger/dagger/pull/3976 | cc1bdc746a82789bb9f2fbc1772e74ff982c294f | a9067a977016f6e8c306d001918aba73d33b168b | 2021-07-29T10:55:06Z | go | 2022-11-23T22:23:26Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 848 | ["go.mod", "go.sum"] | `os.#JSON` package implementation to reinject variables inside cue tree | While working with dagger, I felt the need to process some variables inside a shell script, and reinject them into the cue tree.
As of now, it is only possible with the low level `op` operations, as `os.#File` only retrieves strings. An `os.#Json` or `os.#Export` might be necessary if we want `os.#Container` to beco... | https://github.com/dagger/dagger/issues/848 | https://github.com/dagger/dagger/pull/306 | 12302f7aa13089fe583b58a3bfa3af2418228c76 | 308ade0a794d141ddf0143979bc94cd6af5263af | 2021-07-27T08:08:35Z | go | 2021-04-09T21:03:56Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 832 | ["docs/core-concepts/1218-cli-telemetry.md", "website/sidebars.js"] | Tracking in `dagger` tool, and how to opt out | Our tracking dilemma in a nutshell:
* As open-source *developers*, we need more data about how our software is used, in order to make it better. Solliciting users directly, for example with live interviews and surveys, is useful but not sufficient: we also need tracking. This need is even more acute in the early sta... | https://github.com/dagger/dagger/issues/832 | https://github.com/dagger/dagger/pull/1929 | b32c8732bc7bd932dbdb5dc42fe2434c53cfeb38 | 9f196ca14fa372a2ccd6f192b4c504b799e2c1c4 | 2021-07-16T10:43:26Z | go | 2022-03-29T23:22:17Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 823 | ["state/input.go"] | [BUG] Windows version of 0.19 throw an error on dagger up | I have two environments:
-WSL
-Windows 10
I created an empty workspace (no .cue files), did dagger init and dagger new 'myworkplace'
Expected result:
```bash
user@laptop:/mnt/c/Users/user/.alefesta/dg-orig$ dagger up
1:46PM FTL system | failed to up environment: plan config: no CUE files in .
```
on WSL th... | https://github.com/dagger/dagger/issues/823 | https://github.com/dagger/dagger/pull/1103 | b956ed4d918a409bb6520aafe7fcec1b2b223dc6 | 23d488d4625bb83b9cb9bec4dcf537415e833924 | 2021-07-14T11:55:09Z | go | 2021-11-08T21:20:31Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 801 | ["website/package.json", "website/yarn.lock"] | Parsing: issue with inputs beginning with '--' | When reviewing the netlify package, I generated a personal token which randomly started with `--`.
This led to the encounter of this parsing error:
```shell
$ dagger input secret site.netlify.account.token "--lyYc_hJ*********************" -e multibucket
failed to execute command: unknown flag: --lyYc_hJPbP**
... | https://github.com/dagger/dagger/issues/801 | https://github.com/dagger/dagger/pull/5270 | fe95d0e583204296a96b174b01d317660f95c120 | deed95218e120e6a7e9d57dd095b90216c136610 | 2021-07-09T12:49:09Z | go | 2023-06-02T18:51:53Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 800 | ["sdk/nodejs/package.json", "sdk/nodejs/yarn.lock"] | Persistence keys: help actions manage their own state | This is a proposal for one particular solution to the problem of state persistence in Dagger.
## Problem
Sometimes, a component in the DAG needs to remember what they did earlier - usually so that they can undo it. This feature is called “persistent state” or “state” for short. For example, a component which crea... | https://github.com/dagger/dagger/issues/800 | https://github.com/dagger/dagger/pull/3976 | cc1bdc746a82789bb9f2fbc1772e74ff982c294f | a9067a977016f6e8c306d001918aba73d33b168b | 2021-07-09T11:35:01Z | go | 2022-11-23T22:23:26Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 785 | ["go.mod", "go.sum"] | Implement Serverless Application abstraction on top of AWS Lambda | We need a high-level Application abstraction on top of AWS Lambda, the initial need is for internal tooling (deploy a simple API endpoint without dealing with infra complexity).
Requirements:
- Support Lambda [language-runtimes](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html) and [container ima... | https://github.com/dagger/dagger/issues/785 | https://github.com/dagger/dagger/pull/5545 | 1cb2060cbc7da58bd187f24ea6b340b6dd96762a | 866cf8cb0572df4f0e4aea22bf5375774927dd28 | 2021-07-05T12:56:17Z | go | 2023-08-03T14:28:47Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 770 | ["go.mod", "go.sum"] | discord community link expired or invalid | https://discord.gg/Rmffpmc
link doe not work in readme, is it still active or valid ? | https://github.com/dagger/dagger/issues/770 | https://github.com/dagger/dagger/pull/5459 | bdf0a37ed18007ab47fc9b0445fb20aeade699c9 | 1e7aa6da766b876ca7fb42968186978bdb3a6afa | 2021-07-01T16:50:51Z | go | 2023-07-14T17:58:19Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 745 | ["website/package.json", "website/yarn.lock"] | Locked out of `dagger edit` after removing the wrong field | I removed the `plan.module` field of my environment in `dagger edit`. After that, all commands against that environment failed, including `dagger edit`. This made it impossible to revert my error, short of running `git checkout -f — values.yaml`. I tried editing the file manually but that caused sops errors.
I see 2... | https://github.com/dagger/dagger/issues/745 | https://github.com/dagger/dagger/pull/2818 | 61fd0d795efd73c09f843771df888bce3c616a1d | 196c213575a9b6badbb63c26c0840ff8bd4d34dc | 2021-06-28T13:46:45Z | go | 2022-07-21T09:38:23Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 742 | ["docs/learn/102-dev.md", "docs/learn/106-cloudrun.md", "docs/learn/108-cloudformation.md"] | Tutorials: adopt new “plan outside of environment” coding style | We are deprecating the original method of embedding cue configuration (“the plan”) inside each environment directory. The recommended method is to write Cue configuration in a regular cue module (for example at the root of the repository, or any sub-directory), then reference that configuration in the environment.
O... | https://github.com/dagger/dagger/issues/742 | https://github.com/dagger/dagger/pull/775 | 773f26babeb80a6e8d19e46dd479d90a3ae82acb | 70b2a9e58a04695d8a02bb20f0027ace0b1e5c53 | 2021-06-28T13:23:55Z | go | 2021-07-07T10:00:39Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 739 | ["go.mod", "go.sum"] | Tutorial: specify environment explicitly | Relaying feedback by @amylindburg , thanks Amy!
> If you want the user to simply be able to type in the proposed commands to be successful, then there are a few commands where --environment should be specified (because you end up creating several during the tutorial). But not a biggie.
> `dagger query point --env... | https://github.com/dagger/dagger/issues/739 | https://github.com/dagger/dagger/pull/5459 | bdf0a37ed18007ab47fc9b0445fb20aeade699c9 | 1e7aa6da766b876ca7fb42968186978bdb3a6afa | 2021-06-28T09:40:57Z | go | 2023-07-14T17:58:19Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 733 | ["docs/learn/102-dev.md", "docs/learn/107-kubernetes.md", "docs/learn/108-cloudformation.md", "docs/reference/universe/file.md"] | [Documentation change] dagger doc dagger.io/{module} not working | When we run ```dagger doc dagger.io/netlify``` it throws an error
```FTL system | cannot compile code: cannot find package "dagger.io/netlify"``` for any module.
I tried it with ```dagger doc alpha.dagger.io/netlify```, it was working. Just need to update the doc. | https://github.com/dagger/dagger/issues/733 | https://github.com/dagger/dagger/pull/734 | e16fd88f4c54546f66cfcecd4674d93cff68581c | 53522842edb275f57d3bd647972209b69b4d12ac | 2021-06-27T13:00:10Z | go | 2021-06-27T13:16:46Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 723 | ["sdk/python/requirements.txt"] | Web companion | It would be neat if `dagger` could optionally launch a companion webapp to monitor and configure an environment. This companion webapp would not implement a specific feature, but rather provide a platform for delivering various features that are more appropriate for a web environment. This would allow the CLI to focus ... | https://github.com/dagger/dagger/issues/723 | https://github.com/dagger/dagger/pull/5840 | 49340f005c5eff1a0cf4f3d4becc5c58406d5700 | df982b85b9a60d45468247593271af893dbb63c7 | 2021-06-25T11:39:57Z | go | 2023-10-11T11:55:55Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 722 | ["go.mod", "go.sum"] | Share access to encrypted secrets | Dagger supports encrypting secrets out of the box. But it does not (yet) support controlling who can access which encrypted secret.
Our underlying crypto framework (AGE and SOPS) provides building blocks for very powerful collaboration workflows. Now we have to assemble these building blocks in a particular way, and... | https://github.com/dagger/dagger/issues/722 | https://github.com/dagger/dagger/pull/5459 | bdf0a37ed18007ab47fc9b0445fb20aeade699c9 | 1e7aa6da766b876ca7fb42968186978bdb3a6afa | 2021-06-25T11:36:06Z | go | 2023-07-14T17:58:19Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 719 | ["go.mod", "go.sum"] | Incorrect `missing input behavior` with closed/ redirected stdout | @TomChv realized that one of our Bats test didn't fail on a test with missing inputs :
```bash
# Inside universe dir
# Command that didn't work at first
./node_modules/bats/bin/bats universe.bats -f "docker run: local"
# How to reproduce it locally
dagger up -e docker-run-local >&- # <-- should fail and exit... | https://github.com/dagger/dagger/issues/719 | https://github.com/dagger/dagger/pull/5459 | bdf0a37ed18007ab47fc9b0445fb20aeade699c9 | 1e7aa6da766b876ca7fb42968186978bdb3a6afa | 2021-06-25T00:21:16Z | go | 2023-07-14T17:58:19Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 711 | ["sdk/python/requirements.txt"] | Enforce real names in DCO signoff |
## Summary
Maintainers must check each commit to make sure that the DCO statement (`Signed-off-by: `) includes the real name of the contributor, and not a pseudonym.
## Context
Dagger uses the [Developer Certificate of Origin (DCO)](https://en.wikipedia.org/wiki/Developer_Certificate_of_Origin) process to m... | https://github.com/dagger/dagger/issues/711 | https://github.com/dagger/dagger/pull/5840 | 49340f005c5eff1a0cf4f3d4becc5c58406d5700 | df982b85b9a60d45468247593271af893dbb63c7 | 2021-06-23T08:44:16Z | go | 2023-10-11T11:55:55Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 699 | ["cmd/dagger/cmd/init.go", "cmd/dagger/cmd/list.go", "cmd/dagger/cmd/new.go", "environment/environment.go", "state/state.go", "state/workspace.go", "state/workspace_test.go", "tests/cli.bats", "tests/helpers.bash"] | Default plan directory to `.` | To complete #631: #648 introduced a `--module` and `--package` flag to `dagger new`.
By default, we use `.dagger/env/XXX/plan` as the cue module. Instead, we should default to `.`. | https://github.com/dagger/dagger/issues/699 | https://github.com/dagger/dagger/pull/772 | 21bed8aee69fd4d9547c0c67777eeae7bddcb94d | f8531fdb0b7df9eacf05a52b24dd78e169ca353b | 2021-06-21T15:50:52Z | go | 2021-07-07T15:34:23Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 657 | ["netlify.toml"] | Can’t link to API reference (no index page) | In the API reference section of the docs, each individual package has an address (for example `/reference/universe/alpine`), but there is no address for the API reference as a whole.
* `/reference` returns 404
* `/reference/universe` returns 404
This makes it difficult for other docs pages to link to the APi ref... | https://github.com/dagger/dagger/issues/657 | https://github.com/dagger/dagger/pull/658 | c55f714fec98ed461398e88b4e5c0f218b855c5f | 7403765aacae5f98506286a4075f37d87f573d98 | 2021-06-16T13:31:12Z | go | 2021-06-16T14:04:00Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 627 | ["website/package.json", "website/yarn.lock"] | op: #DockerLogin secret is outdated | Actually, we use the old version of `dagger.#Secret` in `#DockerLogin`
```
#DockerLogin: {
do: "docker-login"
target: string | *"https://index.docker.io/v1/"
username: string
// FIXME: should be a #Secret (circular import)
secret: string | bytes
}
```
That's a real problem because we can't se... | https://github.com/dagger/dagger/issues/627 | https://github.com/dagger/dagger/pull/4224 | 27e735f674d23c87a72d83c6982945b8e8c1a1fe | 9529f2983c2e6d395a21ba91fba715e04342bc22 | 2021-06-12T12:05:14Z | go | 2022-12-20T10:53:09Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 566 | ["docs/current/sdk/nodejs/snippets/yarn.lock"] | `dagger up` shows all intermediary inputs and outputs | `dagger up` now prints the environment’s outputs, which is very useful. However, there is no distinction between “final” outputs and “intermediary” outputs (because we don’t know how to make that distinction). As a result, a typical configuration will print intermediary outputs which are 1) not useful to the end user, ... | https://github.com/dagger/dagger/issues/566 | https://github.com/dagger/dagger/pull/5370 | 72fb1527e9b06ede2c4f5e8eac9a489f5f9e1b7f | 0c8da0a136047f58930ba69d0b5779cfcffb93b7 | 2021-06-04T16:24:36Z | go | 2023-06-26T18:25:03Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 553 | ["sdk/nodejs/package.json", "sdk/nodejs/yarn.lock"] | output list: artifacts are displayed as cue code | This happens with `js/yarn` (e.g. `examples/react`), at the end of `dagger up` (and when using `dagger output list`), artifacts (`docs.build` is a `dagger.#Artifact`) are displayed like this:
```
docs.build {\n from: {\n image: {\n... | https://github.com/dagger/dagger/issues/553 | https://github.com/dagger/dagger/pull/4762 | c28be850965658b1b8e81675500bd6cff439e91f | 98cfa060dafde629cd25d02673908cadb1003a6e | 2021-06-02T22:33:45Z | go | 2023-03-17T15:50:47Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 552 | ["go.mod", "go.sum"] | stdlib: docker.#Push missing features | 1\. `docker.#Push` doesn't support authenticated pushes (and therefore cannot work, unless pushing to a local unauthenticated registry).
Support was added in #373 in `op.#DockerLogin`.
Either `docker.#Push` takes credentials or we expose a `docker.#Login` component.
2\. `docker.#Push` doesn't export the refere... | https://github.com/dagger/dagger/issues/552 | https://github.com/dagger/dagger/pull/5740 | 64f6410e6b9b5dbb1dec82e36de1e674bd7bb856 | d9c7b7b45769c01d6e62e1b835e26bce933fa3b5 | 2021-06-02T22:25:49Z | go | 2023-09-16T09:13:47Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 548 | ["go.mod", "go.sum"] | `dagger up` doesn't rerun buildkit after a manual stop of it's container | After spawning some tty blocking `#op.Exec` commands inside Buildkit for some tests. I wasn't sure if they were still processing in the background.
I manually stopped the buildkit container, then `dagger up` again. However, it didn't reconnect to the buildkit container, neither creates a new one. The only way is to ... | https://github.com/dagger/dagger/issues/548 | https://github.com/dagger/dagger/pull/5740 | 64f6410e6b9b5dbb1dec82e36de1e674bd7bb856 | d9c7b7b45769c01d6e62e1b835e26bce933fa3b5 | 2021-06-02T16:48:17Z | go | 2023-09-16T09:13:47Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 543 | ["go.mod", "go.sum"] | Distinguish core packages from “universe” packages | Dagger distributes several Cue packages for use by the Dagger developer community. There are 2 types of packages:
- Core packages, which expose features of Dagger itself. Currently those are `dagger.io/os`, `dagger.io/file`, `dagger.io/dagger` and `dagger.io/dagger/op`. This may change in the future (possible by mer... | https://github.com/dagger/dagger/issues/543 | https://github.com/dagger/dagger/pull/5845 | df982b85b9a60d45468247593271af893dbb63c7 | 6127466d16229d44214e71417568f9883afcefe4 | 2021-06-02T14:00:26Z | go | 2023-10-11T12:31:59Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 533 | ["website/package.json", "website/yarn.lock"] | `dagger up` fails when docker is not installed | When running `dagger up` on a machine with no docker client installed:
```
$ dagger up
3:26PM ERR system | failed to run docker: exec: "docker": executable file not found in $PATH output=
3:26PM FTL system | unable to create client: exec: "docker": executable file not found in $PATH
```
Tested on https://g... | https://github.com/dagger/dagger/issues/533 | https://github.com/dagger/dagger/pull/2447 | 50e0217049cc44071048f6b385a11d7dcc054011 | c9780a90e0a2e30103176133e61e6a01a6bcbe16 | 2021-06-01T15:27:19Z | go | 2022-05-17T07:08:43Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 532 | ["go.mod", "go.sum"] | failed to load environment: unable to decrypt state: Error getting data key: 0 successful groups required, got 0 | When running `dagger list` in a workspace for which I don’t have the private key, the following error appears: `failed to load environment: unable to decrypt state: Error getting data key: 0 successful groups required, got 0`.
To reproduce, fetch the dagger examples repo, and try to use it:
```
$ git clone https... | https://github.com/dagger/dagger/issues/532 | https://github.com/dagger/dagger/pull/5384 | 70d78ba5e8700d4e885382c7b35efd21482eeac0 | 55f9569ef6a766c5806813491e49be2d829e1453 | 2021-06-01T15:15:57Z | go | 2023-07-03T10:47:40Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 519 | ["Makefile", "cmd/dagger/cmd/version.go", "go.mod", "keychain/keys.go"] | dagger list and other commands that access the env are broken with official release (Mac OS) | Happens only with the official release (not if I compile myself), due to cgo that is disabled.
<img width="675" alt="Screen Shot 2021-05-28 at 2 50 44 PM" src="https://user-images.githubusercontent.com/216487/119986517-c9598500-bf78-11eb-8d67-200a3255f058.png">
Workaround:
```sh
export USER=$LOGNAME
```
I... | https://github.com/dagger/dagger/issues/519 | https://github.com/dagger/dagger/pull/520 | 8d5c3f4f0fa9815f5e9cf59320ec8d8c3f82db1b | e045366e82b3fb352c1f744e9510222ff7a3eb8b | 2021-05-28T12:53:28Z | go | 2021-05-28T19:08:52Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 507 | ["go.mod", "go.sum"] | Personalize 404 error message | Doc website | When visiting an unknown URL (https://docs.dagger.io/devel/deqs), the 404 page retrieved seems in debug mode, showing some S3 infos :
```Code: NoSuchKey
Message: The specified key does not exist.
Key: devel/deqs
RequestId:
HostId: ``` | https://github.com/dagger/dagger/issues/507 | https://github.com/dagger/dagger/pull/340 | e6d96ef5c9cc68a277762d204b32dbc44f019151 | d93c8929cbfa7d3e873ac95e80db65dfe35cefd5 | 2021-05-26T16:42:33Z | go | 2021-04-19T19:33:22Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 506 | ["sdk/nodejs/package.json", "sdk/nodejs/yarn.lock"] | Inconsistent naming in menubar | Doc website | When arriving on the doc website, we can see, on the left, the menubar of all the accessible pages for a given version
**Devel version, left menubar**
```
Introduction
Install Dagger <==
Dagger vs. Other software <==
GUIDES
Programming Guide
Operator Manual
COMMUNITY <==
GitHub
Discord
```
**All other... | https://github.com/dagger/dagger/issues/506 | https://github.com/dagger/dagger/pull/4591 | 89294dbff8caac755a977eb5dfc6df32fa511d52 | 7786ccaa2d687acff4a55f6e1cd36c860804cd96 | 2021-05-26T16:15:54Z | go | 2023-02-14T15:49:31Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 495 | ["sdk/python/poetry.lock", "sdk/python/src/dagger/cli.py", "sdk/python/src/dagger/server/cli.py"] | Broken BuildKit deduplication when using cache mounts | We've had a regression since BuildKit 0.8.3: when using cache mounts, pipelines get executed multiple times (each time they're referenced).
This is because we use the cue value path as "cache key".
https://github.com/dagger/dagger/pull/414 implemented a workaround: if the value is a reference, use the reference a... | https://github.com/dagger/dagger/issues/495 | https://github.com/dagger/dagger/pull/5076 | 7a12edb9a16fb52f5cf14fef1e9ca3540aea3cdc | f6317b608d86bf800defaf71dbf0e4c773b015d4 | 2021-05-25T01:35:22Z | go | 2023-05-04T22:26:08Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 460 | ["website/package.json", "website/yarn.lock"] | The dagger version CLI doesn't require the Global Flags and hence should be removed from the help page |
## Environment
- Macbook Pro Catalina
- Dagger Release Version
```
dagger version --check
dagger version 0.1.0-alpha.5 darwin/amd64
dagger is up to date.
```
## Issue
The ```dagger version``` CLI doesn't require the Global Flags and hence should be removed.
```
dagger help version
Print dagger ver... | https://github.com/dagger/dagger/issues/460 | https://github.com/dagger/dagger/pull/1170 | b2ecc392e576bcb285393026ccf392f71d049f72 | 5533d9561e3e530b43f17c1fbf24abceb44e7b9c | 2021-05-13T06:12:21Z | go | 2021-12-02T23:18:21Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 451 | ["go.mod", "go.sum"] | SIGSEGV when two cue files have different package names in the same environment | Here is my environment:
```
dmp@macArena:~/Projects/Go/src/github.com/blocklayerhq/dagger$ cat ~/.dagger/store/docker-elastic/deployment.json
{
"id": "4d81378c-db20-45fb-a15d-df768d5d336e",
"name": "docker-elastic",
"plan": {
"type": "dir",
"dir": {
"path": "/Users/dmp/Projects/Distributi... | https://github.com/dagger/dagger/issues/451 | https://github.com/dagger/dagger/pull/6572 | 6a3634f6e9b66c124511e07ffc669e3fe5e709ed | 57be8a6f2e65ea108abdc65e58c328365386491a | 2021-05-12T18:28:35Z | go | 2024-02-01T20:31:11Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 449 | ["solver/solver.go", "tests/plan.bats", "tests/plan/client/filesystem/write/test.cue"] | Duplicate log messages | This will naturally run only once ("echo LOL" one time):
```
foo: #up: [
op.#DockerBuild & {
dockerfile: """
FROM dubodubonduponey/debian
ARG TARGETPLATFORM
RUN echo LOL $TARGETPLATFORM
"""
},
]
```
This will run twice (echo LOL multiple time... | https://github.com/dagger/dagger/issues/449 | https://github.com/dagger/dagger/pull/2267 | 92c8c7a2da9ec90a924d7236e540f83ec1f12419 | 2bcd0ac31ce760ce23700b5611fa580aad3c165b | 2021-05-12T17:51:41Z | go | 2022-04-26T18:10:27Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 445 | ["website/package.json", "website/yarn.lock"] | Execution time grows 📈 with config size | It appears that execution time for `dagger up` grows logarithmically with configuration size. When a configuration reaches medium-to-large size, `dagger up` can take several minutes to complete.
This issue can be found, in a more moderate form, when running `cue eval`.
There are many ongoing discussions and inves... | https://github.com/dagger/dagger/issues/445 | https://github.com/dagger/dagger/pull/1141 | 002608b3ba03b7d5defc9b1799bf8fc68c555b3d | 428ce961333f292d977c85cddcbe52d4853596af | 2021-05-11T22:45:26Z | go | 2021-11-17T16:46:43Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 442 | ["Makefile", "tests/README.md"] | `make integration` fails silently when `sops` is not installed | If the [sops](https://github.com/mozilla/sops) tool is not installed, `make integration` will skip all tests which require encrypted inputs, with the confusing error message “skipped: foo/bar/inputs.yaml cannot be decrypted”).
| https://github.com/dagger/dagger/issues/442 | https://github.com/dagger/dagger/pull/443 | 98b3951c7386a8bb62d8a986b9d27a4940367a3d | 2d067c19b43a1ef6e061e9a566f4dca182d57291 | 2021-05-11T21:50:49Z | go | 2021-05-12T18:29:16Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 436 | ["website/package.json", "website/yarn.lock"] | duplication between dagger.io/os with dagger.io/file | #418 added `dagger.io/os` (`#File`, `#Dir`) which duplicates the functionality of `dagger.io/file` (#180).
The two need to be merged together | https://github.com/dagger/dagger/issues/436 | https://github.com/dagger/dagger/pull/1091 | 5e0d582ddd403ac9b55aa90166ae941b9eefa0ae | 1c8ca28b70e336614e403426cc16f4886f8a26ca | 2021-05-08T00:47:27Z | go | 2021-11-09T03:15:24Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 432 | ["dagger/compiler/build.go"] | SIGSEGV on wrong cue syntax | ```
debian: #up: [
op.#DockerBuild & {
dockerfile: """FROM debian
"""
},
]
```
Should have been a new line before FROM - but then, should not SIGSEGV right?
(seems like a cue bug?) | https://github.com/dagger/dagger/issues/432 | https://github.com/dagger/dagger/pull/456 | 668d6ae23f15d672397f85df59f1aa09d8420b20 | 835ac9eef3ff5e710d1472f6afa16d058465689a | 2021-05-07T19:09:54Z | go | 2021-05-12T23:20:32Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 428 | ["go.mod", "go.sum"] | dockerfilePath appears to be misleading or not implemented as it should | `#DockerBuild.dockerfilePath` (apparently: https://github.com/dagger/dagger/blob/62eedd647039f9d237b5be4609f4fe6cb1cda3c8/dagger/pipeline.go#L815) translate to `--option filename` (for buildkit), hence allows simply to specify an alternative name for the Dockerfile, and not to specify an actual path (that part would t... | https://github.com/dagger/dagger/issues/428 | https://github.com/dagger/dagger/pull/5130 | 03ee4e411ab0d590c3c7ac8b6e4221c85174ee68 | 3bb9ca66d347db4d056ed14d0a3c1c4a8e769840 | 2021-05-07T03:42:37Z | go | 2023-05-18T12:09:11Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 396 | ["go.mod", "go.sum"] | Manage digests for docker and git refs | Sometimes my configuration fetches a git or docker repository without specifying a digest, and I want to add the current digest to avoid unexpected changes in the future. But how do I find out the current digest? Dagger does not provide a command to do this. I have to search for specialized tooling and learn how to use... | https://github.com/dagger/dagger/issues/396 | https://github.com/dagger/dagger/pull/5130 | 03ee4e411ab0d590c3c7ac8b6e4221c85174ee68 | 3bb9ca66d347db4d056ed14d0a3c1c4a8e769840 | 2021-04-30T17:51:43Z | go | 2023-05-18T12:09:11Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 364 | ["cmd/dagger/cmd/input/root.go", "cmd/dagger/cmd/input/unset.go", "tests/cli.bats"] | Unset input on deployment | ## Problem
Actually, it's not possible to remove an `input` from a deployment and that's really frustrating...
Imagine an user who do a typo when adding an input ? He will not delete the deployment and restart all from the beggining.
## Proposal
Add a flag `unset` on `dagger input` which take the `cue path` ... | https://github.com/dagger/dagger/issues/364 | https://github.com/dagger/dagger/pull/385 | 9d421c6c4299f6ab6ea147322199e32e87b82a49 | 8abf06cb9bb8764eabc77fe0641e7602e5300b05 | 2021-04-23T14:37:50Z | go | 2021-04-30T18:19:17Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 357 | ["website/package.json", "website/yarn.lock"] | Unique environment ID | Each dagger environment (aka deployment) has a simple name that is only unique locally. There should also be a globally unique ID for each environment. This ID should not depend on the simple name.
If the ID is derived from a unique per-environment keypair (eg. ID = hash of the pubkey), then we can use that keypair ... | https://github.com/dagger/dagger/issues/357 | https://github.com/dagger/dagger/pull/4101 | 1e3e17949c4732b436a2c774043bd9da24cba34a | 302902b8110188c6458295d25be0ac802dba3bdd | 2021-04-22T20:38:51Z | go | 2022-12-06T11:00:45Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 353 | ["stdlib/dagger/op/op.cue"] | `dagger query` is very slow | How to reproduce:
```
cd ./examples/jamstack
# configure app_config.cue
dagger new
dagger up
dagger query # takes 7 seconds on a MBP with M1 proc
```
Likely to be introduced with this commit: https://github.com/dagger/dagger/commit/3e2b46bf3aaefdfe552bb8d42513293a286d0481 (will confirm asap) | https://github.com/dagger/dagger/issues/353 | https://github.com/dagger/dagger/pull/356 | c717af0403d06d9d8fed3199b311bb550d1b3fbf | 4f91907ac4c0aff25687c769a1004aa05efa9120 | 2021-04-22T17:19:31Z | go | 2021-04-22T19:14:37Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 330 | ["website/package.json", "website/yarn.lock"] | Atomic rollouts | When deploying `A` and `B`, if `A` succeeds then `B` fails the rollout is left as is. This can result in a broken deployment since we now have a new version of `A` with an old version of `B`.
Ideally, if a version N of a plan fails, dagger should be re-apply N-1 to bring back `A` and `B` to the same version.
/cc ... | https://github.com/dagger/dagger/issues/330 | https://github.com/dagger/dagger/pull/2639 | 52971518ad4286eff3e00af129de3c30a2f74e51 | a50562519a09249085149214fdb4f444f8387d42 | 2021-04-15T18:10:22Z | go | 2022-06-17T10:19:33Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 316 | ["cmd/dagger/cmd/common/common.go", "cmd/dagger/cmd/compute.go", "cmd/dagger/cmd/down.go", "cmd/dagger/cmd/new.go", "cmd/dagger/cmd/query.go", "cmd/dagger/cmd/up.go", "dagger/client.go", "dagger/pipeline.go", "dagger/solver.go", "examples/jamstack/ecr_image.cue"] | Support command "up --no-cache" to temporarily disable the cache | It's important to be able to to disable the cache on-demand, one-time.
`dagger up --no-cache` | https://github.com/dagger/dagger/issues/316 | https://github.com/dagger/dagger/pull/327 | 551f281bf7bc404a02b01600655cfdc42097880e | 493406afe75277a50478cb4a69cf349674bc1858 | 2021-04-12T21:47:18Z | go | 2021-04-15T18:37:45Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 312 | ["cmd/dagger/cmd/list.go"] | No way to know the current deployment based on local path | We need a way to know the current deployment when working from a local directory. For instance a small `*` or any visual indication when doing `dagger list`. Otherwise, there is no way to know a given directory is mapped to a deployment.
It would also be nice to know which path is mapped to which deployment.
Exam... | https://github.com/dagger/dagger/issues/312 | https://github.com/dagger/dagger/pull/343 | d000b2912b45f927c25a390c53a52823bce06362 | d2d0734eaa926485d6f1e22271b765f9a7a6cc42 | 2021-04-11T02:21:35Z | go | 2021-04-22T18:50:09Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 277 | ["pkg/dagger.io/dagger/engine/fs.cue", "plan/task/source.go", "tests/tasks.bats", "tests/tasks/source/hello.txt", "tests/tasks/source/source.cue", "tests/tasks/source/source_include_exclude.cue", "tests/tasks/source/source_invalid_path.cue", "tests/tasks/source/source_not_exist.cue", "tests/tasks/source/test.sh", "test... | Embed files in a cue configuration | ## Problem
There are two distinct problems caused by the absence of so-called “embedding”.
### Embedding in top-level configuration
Sometimes one wants to embed a Dagger configuration directly in an application repository, in the same way one might embed a Dockerfile or docker-compose.yaml.
This is currentl... | https://github.com/dagger/dagger/issues/277 | https://github.com/dagger/dagger/pull/1312 | 63d655d8f39f08ecc0cd56baed7ff354efbb3ba9 | 4c673aae5291886d715cd025fbd29f6631be2373 | 2021-04-05T21:06:19Z | go | 2022-01-14T09:51:20Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 276 | ["dagger/store.go"] | Multiple deployments with the same name? | It appears multiple deployments can have the same name, which is confusing.
```
$ dagger up
7:50PM FTL system | multiple deployments match the current directory, select one with `--deployment` deploymentPath=/home/shykes/dagger deployments=[
"dagger",
"dagger-dev",
"dagger-dev"
]
```
```
$ ... | https://github.com/dagger/dagger/issues/276 | https://github.com/dagger/dagger/pull/279 | 1ae0ce65e90e4ff3b67317c957636b64058e1f35 | 7cf1163a2b7055a1dae6cdf36aad295398e2487a | 2021-04-05T19:52:47Z | go | 2021-04-06T00:09:35Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 232 | ["sdk/python/poetry.lock"] | Set default loglevel to INFO (not DEBUG) | Now that we are expanding the number of testers, we should not print debug messages by default. This has been confusing to several users.
For example, yesterday I was asked “where is the tarball and where can I retrieve it?”. This is because of a system message from the buildkit exporter producing the tar stream wit... | https://github.com/dagger/dagger/issues/232 | https://github.com/dagger/dagger/pull/5075 | 34e743983cb6290674ff4c2714404e269fdc25d3 | 7c879a2cc5e2c4c41f89ab8d5dd221cc8f9d30d2 | 2021-03-31T22:25:16Z | go | 2023-05-04T22:54:32Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 226 | ["go.mod", "go.sum"] | Store deployment state in a txtar file rather than directory | Cue makes heavy use of the [txtar format](https://pkg.go.dev/golang.org/x/tools/txtar), originally created for the needs of the Go project. It’s a very simple text archive format. It could make our life easier to store deployment state in a txtar file (one file per deployment) rather than in posix directories.
Benef... | https://github.com/dagger/dagger/issues/226 | https://github.com/dagger/dagger/pull/1649 | c207b7e3a92095c866f08d397e201c809d9e90f8 | c82bc00f879919a49a80772a6a3d2ab1de77f2c2 | 2021-03-31T21:40:15Z | go | 2022-03-10T19:00:32Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 186 | ["website/package.json", "website/yarn.lock"] | add lint task to `cue eval` the stdlib | This would help catch some errors earlier. (one I just fixed in #182)
We'd probably want to temp shim in the `cue.mod/dagger.io -> stdlib` symlink for this to work.
Currently it says this:
```
$ cue eval ./stdlib/...
combining bulk optional fields with other fields deprecated as of v0.2.1: try running `cue f... | https://github.com/dagger/dagger/issues/186 | https://github.com/dagger/dagger/pull/1035 | 21eef61983373159e1f8eb21b4a98d4264c81aa5 | badc3a169da5e02cbe6dec73b4419be8723acb7c | 2021-03-16T21:05:04Z | go | 2021-10-04T23:09:01Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 181 | ["sdk/python/poetry.lock"] | Root cmd persistent flags for logging not working | haven't diagnosed completely, but thinking the issue may be with the viper binding(?) | https://github.com/dagger/dagger/issues/181 | https://github.com/dagger/dagger/pull/4394 | 1e54736caeaf9d1f851371178d4f04a93acb545c | 2f8ca6de00299b2714d98f55316ea528b981bbd0 | 2021-03-15T18:19:47Z | go | 2023-01-18T01:08:23Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 151 | ["core/docs/d7yxc-operator_manual.md", "docs/current/faq.md"] | Drop privileges in the managed buildkitd | Right now, when no buildkit address is specified, dagger will create its own instance https://github.com/dagger/dagger/pull/149
The container is created using `--privileged` which is far from ideal. We could look into dropping `--privileged` and using more fine grained `--security-opt`s instead, see:
https://gith... | https://github.com/dagger/dagger/issues/151 | https://github.com/dagger/dagger/pull/5809 | 8f6c3125f14a31e39e251492897c86768147fe26 | e63200db6dd4da2ceff56447d99b01056140b482 | 2021-03-03T19:12:33Z | go | 2023-10-12T22:04:22Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 150 | ["go.mod", "go.sum", "internal/mage/go.mod", "internal/mage/go.sum"] | Rename dagger.#Exec: "dir" to "workdir" | I find `dagger.#Exec: dir` to be confusing. It's not explicitly that it sets the working directory for the command. I would rename it to `workdir` instead.
| https://github.com/dagger/dagger/issues/150 | https://github.com/dagger/dagger/pull/6568 | 01268a5fe62067f7d5dddfb5f5d90ecf4909eac4 | e06291a14e7f694ea2b04c1e30c41ebe751f8f21 | 2021-03-03T03:18:38Z | go | 2024-02-06T12:01:00Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 146 | ["sdk/python/poetry.lock"] | Container Push Support | Currently, there is no way to export an image within a dagger config (e.g. "docker push").
This is extremely limiting -- for instance, it's impossible to deploy a container since it needs to be pushed to a registry before being able to run somewhere.
#134 added support for `#DockerBuild` which is half of the solu... | https://github.com/dagger/dagger/issues/146 | https://github.com/dagger/dagger/pull/4693 | 7ca67e75b0aa064d59bcfca6fafcafc6a3c828c0 | 0345058d089c213b0df646b5e68a307006c5b541 | 2021-03-01T22:10:37Z | go | 2023-03-06T12:00:02Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 142 | ["sdk/python/poetry.lock"] | Docker Image Metadata | #141 added some light support for image metadata
However, this is only half the battle.
If you were to do a FetchContainer followed by a PushContainer (?), all the metadata would be lost.
Regardless of using FetchContainer or not -- if we don't keep track of image metadata during pipeline execution, our result... | https://github.com/dagger/dagger/issues/142 | https://github.com/dagger/dagger/pull/5112 | 0ae172a590ca30eeb86a495cff39bba031887f21 | 0cb0383921a09642d5fddc1096de702fb85fbd6e | 2021-02-25T22:31:41Z | go | 2023-05-05T15:04:07Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 130 | ["go.mod", "go.sum"] | ENV from fetched container is lost | When doing a `#FetchContainer`, `ENV` instructions (such as `PATH`) are lost.
| https://github.com/dagger/dagger/issues/130 | https://github.com/dagger/dagger/pull/6010 | 16b9328aefbc68c3897e503ff24feb8e8ba5de16 | 47837d05154c8d9a12784f9db055b8090980847a | 2021-02-19T08:39:47Z | go | 2023-10-30T14:09:32Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 110 | ["sdk/python/poetry.lock"] | Component validation errors are unintelligible | Let's say that instead of `do: "fetch-container"` we mistakenly type `op: "fetch-container"`, like so:
```
package main
A: #dagger: compute: [
{ op: "fetch-container", ref: "alpine" },
]
```
The generator error looks like this:
> FTL failed to compute error="buildkit solve: invalid task: invalid compon... | https://github.com/dagger/dagger/issues/110 | https://github.com/dagger/dagger/pull/4482 | a317d20b69c2052c397772c74c62460b237e84a8 | e647a6f82310c2cce367c343aed7b999b04916cb | 2021-02-09T00:02:36Z | go | 2023-02-08T18:21:52Z |
closed | dagger/dagger | https://github.com/dagger/dagger | 106 | ["sdk/python/poetry.lock"] | Support multi-arch Components | With the growing number of arm machines, it's critical to support multi-arch builds.
From the simple example in the repo:
```
#alpine: dagger.#Component & {
version: "3.13.1@sha256:3c7497bf0c7af93428242d6176e8f7905f2201d8fc5861f45be7a346b5f23436"
package: [string]: true | false | string
#dagger: compute: [
... | https://github.com/dagger/dagger/issues/106 | https://github.com/dagger/dagger/pull/4646 | 6ffc131f6a3fe03d573586e12eb19226f2a8f41f | faf5b93725d5aae1ab748f6061dc281e112c6313 | 2021-02-06T01:40:07Z | go | 2023-02-24T23:25:52Z |
closed | nektos/act | https://github.com/nektos/act | 2,206 | ["pkg/runner/action_cache.go", "pkg/runner/action_cache_test.go"] | `--use-new-action-cache` doesn't handle `HEAD` | ### Bug report info
```plain text
act version: 4ca35d2
GOOS: darwin
GOARCH: arm64
NumCPU: 10
Docker host: DOCKER_HOST environment variable is not set
Sockets found:
/var/run/docker.sock
Config files:
/Users/jsoref/.actrc:
#... | https://github.com/nektos/act/issues/2206 | https://github.com/nektos/act/pull/2208 | 852959e1e14bf5cd9c0284d15ca899bef68ff4af | 5601fb0e136fad09282705ef65cbc9b2c6f0bebf | 2024-02-05T20:28:03Z | go | 2024-02-18T03:53:22Z |
closed | nektos/act | https://github.com/nektos/act | 2,193 | ["cmd/root.go"] | Crash on version 0.2.58 with "open : no such file or directory" | ### Bug report info
```plain text
act version: 0.2.58
GOOS: linux
GOARCH: amd64
NumCPU: 20
Docker host: DOCKER_HOST environment variable is not set
Sockets found:
/var/run/docker.sock
Config files:
/root/.actrc:
... | https://github.com/nektos/act/issues/2193 | https://github.com/nektos/act/pull/2195 | 3ed38d8e8b63f435cb845fbe9cdccc7ff032f402 | 12c0c4277af1e3d07a6389c3260d28579ba31e01 | 2024-02-01T14:34:35Z | go | 2024-02-01T21:57:16Z |
closed | nektos/act | https://github.com/nektos/act | 2,183 | ["pkg/container/docker_run.go", "pkg/container/docker_run_test.go"] | new-action-cache: rootless containers cannot read actions due to access level | _This is behind a feature flag and doesn't cause problems unless explicit opt in_
Using rootful container avoids the problem | https://github.com/nektos/act/issues/2183 | https://github.com/nektos/act/pull/2242 | 352ad41ad2b8a205b12442859280b0e938b7e4ab | 119ceb81d906be5e1b23bd085f642ffde7144ef5 | 2024-01-30T22:02:18Z | go | 2024-03-08T01:25:03Z |
closed | nektos/act | https://github.com/nektos/act | 2,085 | ["pkg/runner/run_context.go", "pkg/runner/run_context_test.go"] | Job-level `if` ignored when calling a reusable workflow | ### Bug report info
```plain text
act version: 0.2.53
GOOS: darwin
GOARCH: arm64
NumCPU: 12
Docker host: DOCKER_HOST environment variable is not set
Sockets found:
/var/run/docker.sock
$HOME/.docker/run/docker.sock
Config files:
/Us... | https://github.com/nektos/act/issues/2085 | https://github.com/nektos/act/pull/2087 | 04011b6b78c70d36db18419861c737cd0d72d146 | 55477899e70595ec8d8269387643ccca46fd6b38 | 2023-11-10T01:01:16Z | go | 2023-11-12T20:01:32Z |
closed | nektos/act | https://github.com/nektos/act | 2,081 | ["pkg/runner/run_context.go", "pkg/runner/step_test.go"] | Setting `-s GITHUB_TOKEN=...` causes a `GITHUB_TOKEN` env variable to be set in jobs | ### Bug report info
```plain text
act version: 0.2.53
GOOS: darwin
GOARCH: arm64
NumCPU: 12
Docker host: DOCKER_HOST environment variable is not set
Sockets found:
/var/run/docker.sock
$HOME/.docker/run/docker.sock
Config files:
/Us... | https://github.com/nektos/act/issues/2081 | https://github.com/nektos/act/pull/2089 | 610358e1c37630598e5d5022089bc43274ccc997 | 18b4714e38d4871947eff0acb7f1c8f4625fda9f | 2023-11-08T17:19:37Z | go | 2023-11-12T17:52:08Z |
closed | nektos/act | https://github.com/nektos/act | 2,080 | ["cmd/platforms.go", "pkg/runner/run_context.go", "pkg/runner/run_context_test.go"] | `runs-on` does not accept array expressions | ### Bug report info
```plain text
act version: 0.2.53
GOOS: darwin
GOARCH: arm64
NumCPU: 12
Docker host: DOCKER_HOST environment variable is not set
Sockets found:
/var/run/docker.sock
$HOME/.docker/run/docker.sock
Config files:
/Us... | https://github.com/nektos/act/issues/2080 | https://github.com/nektos/act/pull/2088 | 1c16fd1967d68c76aeab6b88d7ac9a6bde1f4123 | 610358e1c37630598e5d5022089bc43274ccc997 | 2023-11-08T16:42:45Z | go | 2023-11-12T17:40:06Z |
closed | nektos/act | https://github.com/nektos/act | 2,017 | ["pkg/exprparser/functions_test.go", "pkg/exprparser/interpreter.go"] | Float formatting doesn't match actions/runner | ### Bug report info
```plain text
act version: 0.2.50
GOOS: darwin
GOARCH: arm64
NumCPU: 12
Docker host: DOCKER_HOST environment variable is not set
Sockets found:
/var/run/docker.sock
$HOME/.docker/run/docker.sock
Confi... | https://github.com/nektos/act/issues/2017 | https://github.com/nektos/act/pull/2018 | 99067a9c1ed3b9cdb75797a7e87e6ef0471105f8 | ace4cd47c7f099864866b1f60e064fecde7f36ea | 2023-09-21T21:08:52Z | go | 2023-10-13T20:01:04Z |
closed | nektos/act | https://github.com/nektos/act | 2,016 | ["cmd/root.go", "pkg/container/docker_socket.go", "pkg/container/docker_socket_test.go"] | --container-daemon-socket and DOCKER_HOST both required with Podman | ### Bug report info
```plain text
❯ gh act --bug-report
act version: 0.2.50
GOOS: linux
GOARCH: amd64
NumCPU: 8
Docker host: unix:///run/user/1000/podman/podman.sock
Sockets found:
/var/run/docker.sock(broken)
$XDG_RUNTIME_... | https://github.com/nektos/act/issues/2016 | https://github.com/nektos/act/pull/2181 | 6e80373eb6a2e87dc228431a7d26c32fa8b4bae9 | f2e65e1d406255cad05b562138758b73219fa74d | 2023-09-21T06:45:20Z | go | 2024-02-06T17:18:11Z |
closed | nektos/act | https://github.com/nektos/act | 2,014 | ["pkg/exprparser/interpreter.go", "pkg/runner/expression.go", "pkg/runner/hashfiles/index.js"] | hashFiles does not resolve paths relative to GITHUB_WORKSPACE | ### Bug report info
```plain text
act version: 0.2.50
GOOS: linux
GOARCH: amd64
NumCPU: 16
Docker host: DOCKER_HOST environment variable is not set
Sockets found:
/var/run/docker.sock
Config files:
/home/mgsk/.actrc:
-P ubu... | https://github.com/nektos/act/issues/2014 | https://github.com/nektos/act/pull/1940 | 2f479ba02470579d32d1cb14f106461063b20726 | 7c7d80ebdd4aee01bb858a828ad864aa120b4a75 | 2023-09-20T18:20:23Z | go | 2023-10-03T22:56:18Z |
closed | nektos/act | https://github.com/nektos/act | 2,003 | ["pkg/runner/run_context.go"] | act does not create separate containers for matrix builds with reusable workflows | ### Bug report info
```plain text
act version: 0.2.50
GOOS: darwin
GOARCH: amd64
NumCPU: 8
Docker host: DOCKER_HOST environment variable is not set
Sockets found:
/var/run/docker.sock
$HOME/.docker/run/docker.sock
Config files: ... | https://github.com/nektos/act/issues/2003 | https://github.com/nektos/act/pull/2015 | 55b09a04cd14006b34eef02f0d19120759ee167b | 1c16fd1967d68c76aeab6b88d7ac9a6bde1f4123 | 2023-09-11T18:38:22Z | go | 2023-11-12T17:21:41Z |
closed | nektos/act | https://github.com/nektos/act | 1,980 | ["go.mod", "go.sum"] | Fails silently when docker is not running | ### Bug report info
```plain text
ct version: 0.2.49
GOOS: darwin
GOARCH: arm64
NumCPU: 8
Docker host: DOCKER_HOST environment variable is not set
Sockets found:
/var/run/docker.sock
$HOME/.docker/run/docker.sock
Config fil... | https://github.com/nektos/act/issues/1980 | https://github.com/nektos/act/pull/838 | a0d360236ef5466a441631c2f93794b55d4b76c5 | b5e8a18683c77c7035c704bb7cec980401c73e18 | 2023-08-21T21:38:44Z | go | 2021-10-18T20:24:05Z |
closed | nektos/act | https://github.com/nektos/act | 1,967 | [".github/workflows/checks.yml"] | Allow node20 in action.yml as action runtime | ### Act version
v0.2.49
### Feature description
See https://github.com/actions/runner/releases/tag/v2.308.0
Since act doesn't care about the version behind `node` why not just exec all `node<number>` via `node`? | https://github.com/nektos/act/issues/1967 | https://github.com/nektos/act/pull/1395 | bd5e0d24d68cddab105ee76bc2fb8000dce76a11 | 37f5b7f4a2bc363be670ee65f623c6b54ec9d8c5 | 2023-08-14T11:20:15Z | go | 2022-10-17T18:14:30Z |
closed | nektos/act | https://github.com/nektos/act | 1,944 | ["cmd/root.go"] | Incorrect podman socket location | ### Bug report info
```plain text
act version: 0.2.46
GOOS: linux
GOARCH: amd64
NumCPU: 8
Docker host: DOCKER_HOST environment variable is not set
Sockets found:
Config files:
Build info:
Go version: go1.20.7
Mo... | https://github.com/nektos/act/issues/1944 | https://github.com/nektos/act/pull/1961 | a00fd960a5d67a21b87ce7f055d9ae89f1603345 | 9f06ca75e447f5fa08de31d2e2577d703df86cc1 | 2023-08-03T07:36:31Z | go | 2023-08-11T05:33:53Z |
closed | nektos/act | https://github.com/nektos/act | 1,894 | [".github/workflows/checks.yml", ".github/workflows/release.yml", ".goreleaser.yml", "Makefile"] | 0.2.47 release was not completed | 👋 it looks like 0.2.47 release was not completed, see [this action run](https://github.com/nektos/act/actions/runs/5428652209/jobs/9873037000), raise this issue for some awareness. Thanks!
relates to https://github.com/Homebrew/homebrew-core/pull/135514 | https://github.com/nektos/act/issues/1894 | https://github.com/nektos/act/pull/1895 | e597046195774991a75ff66506fdfcc3fc903364 | 15618d11874d8f95ffcf10f7cccb013d13e190d6 | 2023-07-03T15:56:23Z | go | 2023-07-10T17:15:16Z |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.