From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Baines Subject: Re: Guix Data Service - September update Date: Sat, 14 Sep 2019 11:51:27 +0100 Message-ID: <87blvnnob4.fsf@cbaines.net> References: <87ftl6k3cn.fsf@cbaines.net> <871rwmr2yk.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:49323) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i95eS-00022h-En for guix-devel@gnu.org; Sat, 14 Sep 2019 06:51:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i95eP-0003XS-LL for guix-devel@gnu.org; Sat, 14 Sep 2019 06:51:36 -0400 In-reply-to: <871rwmr2yk.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s writes: > Hi Chris, > > Christopher Baines skribis: > >> For processing jobs, the records in the database used to be deleted when= the >> job was completed, but now the records are kept and there's a page showi= ng >> jobs [4]. >> >> 4: http://milano-guix-1.di.unimi.it:8765/jobs > > Nice! The page only shows completed jobs, not queued jobs, right? It shows all jobs currently, queued, running and completed (based off the events relating to the job in the database). >> - I want to get back to making progress on automating code review for G= uix >> patches, this was one of the main motivations for getting lint warnin= gs in >> the database and on to the comparison page > > That would be great. In the end, it seems to be that there are quite a > few services we could build around the Data Service. I=E2=80=99m not sur= e how > they should interact. > > For instance, Mumi could talk to data.guix.gnu.org over an HTTP API, or > should we replicate the database at issues.guix.gnu.org so that Mumi can > tap directly into it? It's probably better to use some standard interface like a HTTP API rather than the database directly. What data were you thinking would be useful for Mumi? > Likewise, how should something like hpcguix-web (the package browser at > ) exploit available data, for instance to > show the history of package versions? There are some URLs that can be used to access data, for example this URL should return packages for the latest revision of the master branch [1]. 1: http://data.guix.gnu.org/repository/1/branch/master/latest-processed-rev= ision/packages.json?all_results=3Don Accessing the history of package versions isn't possible yet, but this is something I can look at adding, the information is there in the database. >> - The Guix package and service definitions haven't been merged, so I wa= nt to >> look at that once the location for the Git repository is sorted out > > Looks like it=E2=80=99s done now: > . :-) Yep, and I've gone ahead and reconfigured milano-guix-1, so http://data.guix.gnu.org/ is now the URL. > Are there specific areas where you=E2=80=99d like help? Yes, or rather I have far more ideas than time. I need to get my thoughts in order though and write them down somewhere, maybe a ROADMAP file in the repository, similar to the one in the main Guix repository... > Would you encourage people to start and hack tools or services that > build upon the available data? Yes, although I'm still unsure how stable the API will be, so that's an important thing to keep in mind. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAl18xi9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE 9XeQYA//UXor9+m6LsXM6ib3tjpzCRsIGcGfwQZ3c6pKn+rwofK3peQEAVnwEsk4 c2MbnlRBOf59yojS3zZd2BPEG1qErCSutPTjVuuYKe0yNRgNMuPLwpTzC3fqaB+c 9aknrY3OU21AbvWyFs5D7iBxRFQfxIF5nVoN7mofQfPIACW56RnFY4b55GEbpSuP 1W0kXZnDm17+VSKc6yUpgy5RVJD9+xhx3l9aQ82Mfg/oPP2kepgQf0XzBRmB/fmF vB2E4zlpY7EOk5+mtPEKxu//LH4y9seTxvkqtvQ5+FEa0narg5WLoYfrSSldggwv NQoAeC919STDdsUsIzNm+Pz5ze6QVvgWFWDsKIkstcSkzHUNja7RBYLdMZ9aGw/7 gqHKtpAzdgz+CGmn9dWYzczfkobS6P5wR64Wnh7Qt8pfa2RNRZfogFdHzgajoGFh Q8RNN3+VZmm75xlNq/PgJjKaNWYspuiwXjEhxVj60b1yXtBkV6BpQa9rHVR/NX3P 7VHKHSZl0XL+V2CJdWwv5w2oy9husD4kyx7UGWl033sP7rK+unnlEq6TAnWUx8Cx 3OfPDNUhcQIeneaNspchrkPPYbZLDAVLwX2ceS50/ufGBu3xXB8b7PaPURMuqKnj PNsZ/MD6l2wuK7TG5e8uINPAeGPnoyv3uo7Ik1lVCOGey+N51EQ= =jRm8 -----END PGP SIGNATURE----- --=-=-=--