unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Ricardo Wurmus <rekado@elephly.net>, gwl-devel@gnu.org
Subject: Re: Preparing for a new release
Date: Mon, 10 Feb 2020 08:34:03 +0100	[thread overview]
Message-ID: <CAJ3okZ2tfrme43jxyZsYfReJ2gErLdja2AmnkoCHO76hL44ODw@mail.gmail.com> (raw)
In-Reply-To: <87tv3z2pyf.fsf@kyleam.com>

On Mon, 10 Feb 2020 at 02:25, Kyle Meyer <kyle@kyleam.com> wrote:
>
> zimoun <zimon.toutoune@gmail.com> writes:
>
> > On Sun, 9 Feb 2020 at 14:01, Ricardo Wurmus <rekado@elephly.net> wrote:
> >
> >> * inputs and outputs are not validated
> >>
> >>   When a process declares that it produces an output, but then doesn’t do
> >>   that, the next process will fail with a nasty error message.  This is
> >>   especially nasty when using containerization as the error is about
> >>   failing to map the input into the container.
> >>
> >>   Processes should automatically validate their inputs and outputs.
> >>   Since inputs and outputs could technically be something other than
> >>   files I’m not sure exactly how to do this.
> >
> > From my understanding, Snakemake uses only files as inputs/outputs.
> > But I do not know what happens if 'rule 1' claims to output 'file' and
> > 'rule 2' says its input is 'file' and then 'rule 1' never produces
> > this file 'file'; the 'rule 2' is never processed, I guess. Hum? need
> > to check...
>
> In that case, an exception is raised:
>
>     Waiting at most 5 seconds for missing files.
>     MissingOutputException in line 2 of /tmp/snakemake-hAlqJ/Snakefile:
>     Missing files after 5 seconds:
>     foo
>     This might be due to filesystem latency. If that is the case, consider
>     to increase the wait time with --latency-wait.
>     Shutting down, this might take some time.

Thank you for checking.


All the best,
simon

  reply	other threads:[~2020-02-10  7:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-08 12:39 Preparing for a new release Ricardo Wurmus
2020-02-08 20:38 ` Kyle Meyer
2020-02-08 21:50   ` Ricardo Wurmus
2020-02-09 13:00     ` Ricardo Wurmus
2020-02-09 23:33       ` zimoun
2020-02-10  1:25         ` Kyle Meyer
2020-02-10  7:34           ` zimoun [this message]
2020-02-10  6:31         ` Ricardo Wurmus
2020-02-10  7:43           ` zimoun
2020-02-10 21:28             ` Ricardo Wurmus
2020-02-10 23:43               ` zimoun
2020-02-11  9:39                 ` Ricardo Wurmus
2020-02-11  9:34               ` Ricardo Wurmus
2020-02-11 15:37                 ` zimoun

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=CAJ3okZ2tfrme43jxyZsYfReJ2gErLdja2AmnkoCHO76hL44ODw@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=gwl-devel@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=rekado@elephly.net \
    /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).