From: Christopher Baines <mail@cbaines.net>
To: Luciana Lima Brito <lubrito@posteo.net>
Cc: guix-devel@gnu.org
Subject: Re: Guix Data Service - Outreachy: questions about render-compare/derivation
Date: Tue, 13 Apr 2021 22:06:55 +0100 [thread overview]
Message-ID: <878s5lzyfk.fsf@cbaines.net> (raw)
In-Reply-To: <20210413164501.1626ecc4@lubrito>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
Luciana Lima Brito <lubrito@posteo.net> writes:
> Just to report my progress and ask some more questions.
> I attached a new image of the json I have by now.
Good good :)
> I still have to find a way to use a proper name instead of the 0 and 1
> of the array. Another thing that I'm still looking into is why the
> "source" field displays the value of the derivations as a name in the
> hierarchy, instead of a string.
It looks like the 0 and 1 thing is only an issue for the outputs and
inputs now, which is good.
As for how the sources end up like that, I think a list with a single
string might end up like that. Maybe try comparing a derivation to
itself (not a very useful query, but it might help generate some new
data to work with).
> All the fields are being displayed in the json, but I don't know all the
> values the fields can assume, so I don't know exactly which tests I
> should do. In the .html file I could see that many more test are
> performed to get the same values I got for the json, so probably I'm
> missing some, I will look into this, however, for all derivations
> comparisons I checked the values seem correct.
Sounds good,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2021-04-13 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 15:14 Guix Data Service - Outreachy: questions about render-compare/derivation Luciana Lima Brito
2021-04-12 19:41 ` Christopher Baines
2021-04-13 19:45 ` Luciana Lima Brito
2021-04-13 21:06 ` Christopher Baines [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878s5lzyfk.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=lubrito@posteo.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).