-
digdag should complain about incorrectly placing `_schedule` outside the workflow like this:
```
run: +main
_schedule:
hourly>: 12:34
+main:
td>: query/important.sql
```
-
Many operators need parameters such as hostname, password, etc. They are connection information. We don't want to put those information in workflow yml file because those files could be uploaded to gi…
-
When I ran a workflow on Digdag server running in localhost, this error occurred.
```
2016-04-05 11:21:09 +0900 [INFO] (0037@+main+step1): sh>: ./tasks/bin/enc-tool -e development-ec2 -a 1 -c ENCRYPT…
-
_[Original issue](https://code.google.com/p/guava-libraries/issues/detail?id=1527) created by **thomas.lorblanches** on 2013-09-11 at 12:49 PM_
---
I had no problem previously with Guava 14.0.1, but…
-
```
$ cat digdag.yml
run: +main
timezone: "America/Los_Angeles"
+main:
_schedule:
cron>: 42 4 1 * *
sh>: echo hello world
```
```
$ digdag push dano-cron-test -r 1
2016-04-11 15:46:26 -0700…
-
-
so that `digdag push` excludes those files.
-
digdag tasks are defined in a key-value map and digdag executes tasks in the literal order of the text in the yaml file. This can be fragile as key-value maps in YAML do not have a well defined semant…
-
Hi @staticfloat, thanks for helping me out. I ran `using BinDeps` before trying to build ImageMagick.
```
julia> versioninfo()
Julia Version 0.5.0
Commit 3c9d753 (2016-09-19 18:14 UTC)
Platform I…
hpoit updated
7 years ago
-
I.e., the below workflow definition should fail instead of silently just executing `echo bar`.
``` yaml
run: +foo
+foo:
sh>: echo bar
py>: baz
```
Also, it might be worth considering if multiple…