On Sunday, 18 April 2021 at 04:09:22 UTC+10 [email protected] wrote: > On Saturday, April 17, 2021 at 6:07:01 AM UTC-7 mwall wrote: > > the quantity of information is not a problem. users' ability to run the > tool and post the output is the problem. lets make that easier. > > Agree. Maybe that's the real problem why it's not used much. >
We have words at the top of the weewx-user page tell users to post certain details, they frequently don’t. I suspect the real reason that wee_debug is not used is because users don’t know about it and those that do ignore it. I don’t believe we will easily change that (user) behaviour. I am resigned to having to tell users to use it just as we have to tell them to include a log extract or set debug=1. > probably worthwhile for wee_debug to run a second obfuscation pass after >> it has generated its output. that would catch commented items. >> > > The obfuscation uses ConfigObj, so some other method using regex or the > like would be needed for stronger obfuscation. I'd suggest removing all > whitespace lines, all lines with whitespace+comments, and even all comments > at the end of a line to make it 'really' certain it's obfuscated. > Configobj is just used to parse weewx.conf and obtain a dict. Everything is there, comments and all but the obfuscation code only looks for dict keys that start with the item of interest. It could be as simple as changing a ‘startswith’ to ‘in’, certainly should not be difficult. how weewx was installed is pretty obvious from weewx.conf combined with the >> first few lines of the log output. and that is direct, not inferred >> information. >> >> > > In general, yes, but we've seen folks with multiple installations (one > setup, one packaged) and wee_debug only reports based on the .conf file you > tell it to use. This is why I'm suggesting to just check for both places > weewx.conf might be present in, just in case, and flag it if it finds two > installations present. > They beauty of wee_debug is that it gives you the config, details etc for the WeeWX install that will be run if the user starts WeeWX in the usual way. So we are not relying on th3 user to determine what is being run. This is often overlooked and I believe a strength of wee_debug. By all means state if there are multiple install types but wee_debug should continue to only provide details on the ‘default’ install. The other thing to note is that how you call wee_debug matters especially > when looking for python dependencies. Did I add pyephem via package or pip > ? > > You have to call it with the interpreter weewx is configured to use. In > my example, I have a native python2 system that I added python3 to manually > by compiling my own. The system default is python2. So I had to run > 'python3 /home/weewx/bin/wee_debug' for it to work. Perhaps an edge case > nowadays as most systems other than RedHat.old are native python3 finally. > wee_debug is no different to any of the other utilities, if you need a special incantation for wee_debug you will need the same incantation to run wee_database, wee_reports etc. > > (re: your other followup) > > Not sure how to work posting to the weewx-user group. None of my weewx > systems have 'ever' been able to email anywhere, nor will they. > > Of course if you wanted to go clean sheet of paper, we could generate JSON > debug output that some future automated processor could reduce and flag > errors on, but that leads you down a much longer path. > I’m not sure I see the benefit of emails, pdfs, json etc. if the wee_debug out is dumped to a text file it can be transferred and posted anywhere without need to more software. Looking at the wee_debug code again I think the piping to file may have been affected by the python 2/3 conversion. I see a few six compatibility calls in and around the writing to stdout. We might have to revisit how that is done. Gary -- 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/ac51011a-a3cc-4284-9a85-3be7cd3c08b2n%40googlegroups.com.
