From: Tatiana Sholokhova <tanja201396@gmail.com>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Web interface review
Date: Sun, 22 Jul 2018 16:57:18 +0200 [thread overview]
Message-ID: <CAMSS15DSiv9VRAVagHAScjn3f=8wX3DWpxDYvhnTcqZBfkkHYA@mail.gmail.com> (raw)
In-Reply-To: <87h8ksmyn4.fsf@lassieur.org>
[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]
Hi Clement,
Thank you for your advice! I resolved the 'with-critical-section' issue. To
do so, I had to remove 'with-critical-section' call from
'handle-build-request' function and wrap critical section around each call
of this function.
Today I am trying to fix the pagination and I will let you know about my
results.
P. S.
Now I send this changes as separate small commits, we can rebase the
history again when I finish with pagination.
Best regards,
Tatiana
сб, 21 июл. 2018 г. в 16:50, Clément Lassieur <clement@lassieur.org>:
> Hello Tatiana!
>
> Tatiana Sholokhova <tanja201396@gmail.com> writes:
>
> > Hello Clément!
> >
> > Thank you for your review!
> >
> > I fixed most of the problems you noticed and rebased commits as you
> advised
> > .
> >
> > I couldn't fix the problem with several calling of
> (with-critical-section).
> > As I wrote to IRC channel, I tried to put '(with-critical-section
> > db-channel (db)' around '(let* ...)' and I received an error:
> > ```
> > In web/server.scm:
> > 279:25 0 (_)
> > Throw to key `vm-error' with args `(vm-run "Too few values returned to
> > continuation" ())'.
> > ```
>
> It's because 'respond-html' returns several values. I think you could
> do:
>
> (respond-html
> (with-critical-section ...
> (let* ...)))
>
> > Could you give a status about the pagination?
> >>
> > Pagination works correctly with evaluations, but it doesn't work
> correctly
> > with builds. In some cases, we have builds missing. It happens due to
> equal
> > timestamp values, so we need to filter build by (timestamp, id) tuple
> key.
> >
> > What else do we need to do before the merge?
>
> Once we have something consistent, we can push. And we can add stuff
> afterwards of course. Do you think it would be feasible to fix the
> pagination before the merge?
>
> I won't have time to look at your update before tomorrow night, I'll let
> you know then!
>
> Thanks,
> Clément
>
[-- Attachment #2: Type: text/html, Size: 2843 bytes --]
next prev parent reply other threads:[~2018-07-22 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 21:23 Web interface review Clément Lassieur
2018-07-20 8:59 ` Gábor Boskovits
2018-07-20 9:28 ` Clément Lassieur
2018-07-21 14:08 ` Tatiana Sholokhova
2018-07-21 14:50 ` Clément Lassieur
2018-07-22 14:57 ` Tatiana Sholokhova [this message]
2018-07-22 22:56 ` Tatiana Sholokhova
2018-07-27 20:44 ` Clément Lassieur
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='CAMSS15DSiv9VRAVagHAScjn3f=8wX3DWpxDYvhnTcqZBfkkHYA@mail.gmail.com' \
--to=tanja201396@gmail.com \
--cc=clement@lassieur.org \
--cc=guix-devel@gnu.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.
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).