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 16:10:45 +0100 [thread overview]
Message-ID: <874kvpmeq2.fsf@elephly.net> (raw)
In-Reply-To: <875zg5mgzr.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi Jelle,
>
> thanks for giving the GWL a try!
>
>> How do I install GWL, while using a `guix pull'-managed guix (so with
>> guile3.0)? As the `guix' that is a propagated input still uses guile2.2,
>> this is not as simple as I had hoped it would be.
For now I think we could provide a guile3.0-gwl variant in Guix using
guile3.0-guix as an input. (Or rather default to Guile 3 and provide a
guile2 variant.)
>> My other issue relates to actually running computations usings
>> GWL. Given the following workflow file:
>>
>> --8<---------------cut here---------------start------------->8---
>> process hello-world
>> # { echo "Hello, world!" }
>>
>> workflow do-the-thing
>> processes hello-world
>> --8<---------------cut here---------------end--------------->8---
>>
>> I can run GWL to both prepare and graph my workflow, yet I get the
>> following backtrace when trying actually `gwl --run=<file>': […]
>
> Oh, I’m sorry! This is a bug. The code was supposed to pass a list of
> mapped input files to a procedure, but it accendentally just passed a
> boolean. That’s clearly incorrect. I’m going to fix this soon.
>
> So I suppose we’ll see a 0.2.1 release soon… Sorry about that!
I fixed the bug locally, but I want to add a few more tests for that
part of the code before pushing it.
--
Ricardo
next prev parent reply other threads:[~2020-02-17 15:11 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 [this message]
2020-02-17 18:31 ` Jelle Licht
2020-02-17 19:53 ` Ricardo Wurmus
2020-02-17 22:55 ` Ricardo Wurmus
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=874kvpmeq2.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).