Gary, I already did the same validation and came to the same doubt as stated below... Something went wrong with the sync.
Regards, \Leon -- Leon Shaner :: Dearborn, Michigan (iPad) > On Nov 16, 2019, at 9:39 PM, gjr80 <[email protected]> wrote: > > > Are you sure you have picked up development? I just searched through restx.py > and wunderfixer in the development branch and there are no apikey entries > (well apiKey is used in a URL but this has nothing to do with the config > option name), everything is api_key. I would be very surprised to see this > config option change names, it would break backwards compatibility for a > start. > > Gary > >> On Sunday, 17 November 2019 12:31:17 UTC+10, Leon Shaner wrote: >> Gary, >> >> I had just done a new sync this afternoon from the latest development. >> That introduced a disagreement as to whether the property should be api_key >> as I had it, or apikey as the newly sync'd code was expecting. >> I figured Tom had taken a different path and decided to use apikey afterall, >> because that's what restx.py was expecting. >> >> So I changed from api_key to apikey in the weewx.conf to make the code work. >> Then in wunderfixer I also had to change where it expected api_key to use >> apikey. >> >> In retrospect, I probably should have fixed restx.py instead since I can now >> see that wee_debug is also expecting api_key, not apikey. :-/ >> >> Ugg and now I see that restx.py expects apikey in my local copy, but when >> viewing it on github it expects api_key. >> >> So I think github failed me in some regard w.r.t. the pull from development >> branch to my fork, to my local copy. :-( Likely user error, but it pulled >> over 200 changes then told me I was up to date. :-/ >> >> Net net, sorry for the noise about api_key not being obfuscated. >> I'm off to sort out why I'm not actually running the latest sync I thought I >> was running. :S >> >> I suppose some other part of the code could have been out of sync too, >> leading to the timestamps being off by an hour / overlapping with data in >> the same hour from prior to the upgrade. :-/ >> >> Regards, >> \Leon >> -- >> Leon Shaner :: Dearborn, Michigan (iPad) >> >>>> On Nov 16, 2019, at 9:19 PM, gjr80 <[email protected]> wrote: >>>> >>> >>> Would appreciate some more info on this, I just used 4.0 wee_debug it it >>> obfuscated a new WU API key as expected. The obfuscation code is pretty >>> basic, for WU it is if key name == 'api_key' then value with 'XXX >>> obfuscated by wee_debug XXX'. I seem to remember you changing WU config >>> option names some time ago, what is the config option name that failed, I'm >>> betting it was not 'api_key'. >>> >>> Gary >>> >>>> On Sunday, 17 November 2019 11:37:24 UTC+10, Leon Shaner wrote: >>>> >>>> BTW, wee_debug is not obfuscating the new WU apikey property. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "weewx-development" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-development/b762f6cd-7e78-444e-b80c-e8009f003b7c%40googlegroups.com. > > -- > You received this message because you are subscribed to the Google Groups > "weewx-development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-development/184f59d7-eca8-4f60-bc44-68d3edceebb3%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/DB64D069-45AE-4558-8BBF-AF0E633C029C%40isylum.org.
