unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Jelle Licht <jlicht@fsfe.org>
Cc: gwl-devel@gnu.org
Subject: Re: How to get started using GWL 0.2.0
Date: Mon, 17 Feb 2020 23:55:20 +0100	[thread overview]
Message-ID: <87v9o4lt7r.fsf@elephly.net> (raw)
In-Reply-To: <8736b9m1nc.fsf@elephly.net>


Ricardo Wurmus <rekado@elephly.net> writes:

> Jelle Licht <jlicht@fsfe.org> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> Ricardo Wurmus <rekado@elephly.net> writes:
>>>
>>> [...]
>>> I fixed the bug locally, but I want to add a few more tests for that
>>> part of the code before pushing it.
>>
>> I'd still like to play around with any (temporary) workaround you might
>> have. Would you be willing share it as a patch that I can apply locally?
>
> Oh, certainly.  The reason for the bug is that I didn’t bother testing
> workflows without any inputs.  The temporary workaround is to add an
> input, even if you aren’t using it:
>
> --8<---------------cut here---------------start------------->8---
> process hello-world
>   inputs "/tmp"
>   # { echo "Hello, world!" }
>
> workflow do-the-thing
>   processes hello-world
> --8<---------------cut here---------------end--------------->8---
>
> Sorry about this!

This is now fixed in commit 6d050d9937f4a454b5e051640a8831fb5035c758.
Still working on extending the test suite…

-- 
Ricardo

      reply	other threads:[~2020-02-17 22:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17  9:59 How to get started using GWL 0.2.0 Jelle Licht
2020-02-17 14:21 ` Ricardo Wurmus
2020-02-17 15:10   ` Ricardo Wurmus
2020-02-17 18:31     ` Jelle Licht
2020-02-17 19:53       ` Ricardo Wurmus
2020-02-17 22:55         ` Ricardo Wurmus [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.guixwl.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v9o4lt7r.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=gwl-devel@gnu.org \
    --cc=jlicht@fsfe.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).