GNU bug report logs -
#26373
Various improvements to the CRAN importer
Previous Next
Reported by: Ricardo Wurmus <rekado <at> elephly.net>
Date: Wed, 5 Apr 2017 16:41:01 UTC
Severity: normal
Done: Ricardo Wurmus <rekado <at> elephly.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Tue, 16 May 2017 21:48:16 +0200
with message-id <87shk4a8hr.fsf <at> elephly.net>
and subject line Re: bug#26373: [PATCH 6/6] import cran: Skip updating when meta data cannot be downloaded.
has caused the debbugs.gnu.org bug report #26373,
regarding Various improvements to the CRAN importer
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
26373: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26373
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
The following patch series improves the CRAN importer.
[Message part 3 (message/rfc822, inline)]
Ludovic Courtès <ludo <at> gnu.org> writes:
> Ricardo Wurmus <rekado <at> elephly.net> skribis:
>
>> Ludovic Courtès <ludo <at> gnu.org> writes:
>>
>>> Ricardo Wurmus <rekado <at> elephly.net> skribis:
>>>
>>>> * gnu/packages/bioinformatics.scm (latest-cran-release,
>>>> latest-bioconductor-release): Abort early when meta data cannot be downloaded.
>>>> ---
>>>> guix/import/cran.scm | 6 ++++--
>>>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/guix/import/cran.scm b/guix/import/cran.scm
>>>> index 557d694ad..fc7a1ed84 100644
>>>> --- a/guix/import/cran.scm
>>>> +++ b/guix/import/cran.scm
>>>> @@ -398,7 +398,8 @@ dependencies."
>>>> (package->upstream-name package))
>>>>
>>>> (define meta
>>>> - (fetch-description 'cran upstream-name))
>>>> + (false-if-exception
>>>> + (fetch-description 'cran upstream-name)))
>>>
>>> I would prefer catching only the relevant exception. So I suppose
>>> something like:
>>>
>>> (guard (c ((http-get-error? c)
>>> (if (= 404 (http-get-error-code c))
>>> #f
>>> (raise c))))
>>> (fetch-description 'cran upstream-name))
>>>
>>> However I see that ‘fetch-description’ already does that, so what
>>> exceptions are we protecting against?
>>
>> I don’t know what the desired behaviour here is. When updating
>> packages, I think it’s good to keep going. If there’s an error
>> downloading the package meta data I want “meta” to be “#f”, which leads
>> to skipping the update.
>>
>> Without turning errors to “#f” I wasn’t able to just update all packages
>> with “guix refresh -t cran,bioconductor -u”.
>
> What was the exception?
>
> I think a good approach is to catch precisely the kind of error that we
> don’t want to see. ‘false-if-exception’ catches everything and could
> thus hide genuine errors/bugs (including unbound variables and similar),
> which sounds undesirable.
>
> WDYT?
I don’t remember why I wanted this, so I didn’t push this patch. I
agree that it’s much better to catch errors precisely.
Thanks for the review! I pushed all the other patches (with the
exception of one that Mathieu had already implemented independently) to
master.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
This bug report was last modified 8 years and 65 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.