| To: | Marko Myllynen <myllynen@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pmrep: fix timezone handling/reporting |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Mon, 8 Feb 2016 00:39:05 -0500 (EST) |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <56AF6E49.1040404@xxxxxxxxxx> |
| References: | <56AF6E49.1040404@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | qhuXwcbeYvSX7bfDakj9SCA80PFXBA== |
| Thread-topic: | pmrep: fix timezone handling/reporting |
Hi Marko, ----- Original Message ----- > Hi, > > I think this works in every case without even hitting the previously > reported issues (no workarounds required for that). Since this is not > the first attempt on this front I'm not updating QA myself, hoping > to get a review for this before QA test data update. > It looks like we're dealing with the PMAPI notion of the timezone not being in sync with what some python modules think the tz is? The way the pm*Zone works is setting $TZ under the covers (see pmUseZone code in libpcp). 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). So if we cannot use the helper APIs then this patch looks OK to me. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | patch/RFC - pmrep: handling broken pipe and Exception Ignored errors, Mark Goodwin |
|---|---|
| Next by Date: | Re: [pcp] patch/RFC - pmrep: handling broken pipe and Exception Ignored errors, Marko Myllynen |
| Previous by Thread: | pmrep: fix timezone handling/reporting, Marko Myllynen |
| Next by Thread: | Re: [pcp] pmrep: fix timezone handling/reporting, Marko Myllynen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |