pcp
[Top] [All Lists]

Re: [pcp] pmrep: fix timezone handling/reporting

To: Marko Myllynen <myllynen@xxxxxxxxxx>
Subject: Re: [pcp] pmrep: fix timezone handling/reporting
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Mon, 8 Feb 2016 16:50:36 -0500 (EST)
Cc: pcp developers <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <56B8A997.6070903@xxxxxxxxxx>
References: <56AF6E49.1040404@xxxxxxxxxx> <2118214472.19115278.1454909945154.JavaMail.zimbra@xxxxxxxxxx> <56B8A997.6070903@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: AUcPUWT9UEqyhaxbC5Y+1t8QlShXug==
Thread-topic: pmrep: fix timezone handling/reporting
Hi Marko,

----- Original Message -----
> [...]
> > As discussed in that other thread, we've managed to avoid some helper
> > routines in pmrep (pmGetContextOptions in particular) which might've
> > made some of this easier, not sure (if we are really out of sync, we
> > will not be helped by that I guess).
> 
> One reason why we've avoided using pmGetContextOptions in pmrep is that
> it's not available via the Python PMAPI :-)

Its there, its just not directly called - pmContext.fromOptions builder
interface makes use of it (hmm, which pmrep already uses?) via:

        # finish time windows, timezones, archive access mode
        if c_api.pmSetContextOptions(context.ctx, options.mode, options.delta):
            raise pmUsageErr

(which internally calls pmGetContextOptions)

> > So if we cannot use the helper APIs then this patch looks OK to me.
> 
> Perhaps we could start with this then to get the situation under control
> and later on consider pmGetContextOptions if it becomes available and
> makes the code easier to read?

Sure.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>