Hi Roel,
Thank you for all your comments.
> Maybe we can come up with a convenient way to combine two processes
> using a shell pipe. But this needs more thought!
Yes, from my point of view, the classic shell pipe `|` has two strong
limitations for workflows:
1. it does not compose at the
Leo Famulari writes:
> On Tue, Jul 17, 2018 at 11:36:08AM -0400, Leo Famulari wrote:
>> Quoting Greg Kroah-Hartman:
>>
>> "I did this release anyway with this known problem as there is a fix in
>> here for x86-64 systems that was nasty to track down and was affecting
>> people. Given that the
Dear all,
Ludovic Courtès writes:
> Hello Tatiana & all,
>
> Ricardo Wurmus skribis:
>
>>> I am a bit confused about the database structure. As far as I understand,
>>> there are project_name (project) and branch_name (jobset) properties, but
>>> project_name is a primary key, so a project
Hello Simon,
zimoun writes:
> Hi,
>
> I am asking if it should be possible to optionally stream the
> inputs/outputs when the workflow is processed without writing the
> intermediate files on disk.
>
> Well, a workflow is basically:
> - some process units (or task or rule) that take inputs
On Wed, Jul 18, 2018 at 03:11:36PM +0200, Pierre-Antoine Rouby wrote:
> I thinks the modifications doesn't works on my computer.
>
> ---
> Backtrace:
> 13 (apply-smob/1 #)
> In ice-9/boot-9.scm:
> 705:2 12
Hi Tatiana,
Tatiana Sholokhova writes:
> Am I right that in terms of Cuirass database derivations correspond to
> jobs?
Yes, but to be more precise, a job is a structure containing:
- derivation
- job-name
- system
- nix-name
- eval-id
The database table called "Derivations" should
Hi Tatiana,
Tatiana Sholokhova writes:
> Could you please review the last 3 commits and maybe find some more issues
> besides that?
I've integrated your work onto my Cuirass instance[1], and I really like
it! I had to fix a few things and adapt it[2] so that it works with
multiple inputs.
I
Hi,
I am asking if it should be possible to optionally stream the
inputs/outputs when the workflow is processed without writing the
intermediate files on disk.
Well, a workflow is basically:
- some process units (or task or rule) that take inputs (file) and
produce outputs (other file)
- a
Hi Leo,
- Original Message -
> From: "Leo Famulari"
>> * guix/import/gopkg.scm: New file.
>> * guix/scripts/import/gopkg.scm: New file.
>> * guix/scripts/import.scm: Add 'gopkg'.
>> * Makefile.am: Add 'gopkg' importer in modules list.
>
> I wonder which of the new files needs to be
