weectl report run single_report_name Runs More Than Single Report

[gary....@gmail.com]

I've been installing various versions of a skin. I erase the skin and html directories for the skin, install, the run weectl report run new-belchertown

I'd expect that it would run just the new-belchertown skin and be done.

Instead this seems to run everything under [stdRESTful] as well.

See attached for the journal entries for 2 runs.

[John Smith]

Instead this seems to run everything under [stdRESTful] as well.

Yes, I'd noticed this as well, I'm guessing the assumption made is those services may be needed to facilitate report generation, maybe file an issue and/or PR adding a switch to weectl so it can skip loading and running them if not needed.

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/c5a4bda2-00f3-45a4-b458-49886f81a1f3n%40googlegroups.com.

[R]

I think you will find it is all about ensuring the xtypes are loaded and available for the report engine used by weectl report run. weectl report run uses a dummy engine that loads all services as per weewx.conf, but never actually 'runs' the engine, so the loaded services don't actually do anything. Sure, you could have the dummy engine not load a few services to save a few bytes and microseconds, but since weectl report run is run and done in a few seconds it sounds like added complexity for little to no benefit.

R

[gary....@gmail.com]

Ah, I see. No problem then.

[Tom Keffer]

R has it exactly right. 

In particular the RESTful services get loaded because it is possible that one or more of them is responsible for installing an xtype.

On Fri, Jul 10, 2026 at 1:14 AM R <mrsn...@gmail.com> wrote:

I think you will find it is all about ensuring the xtypes are loaded and available for the report engine used by weectl report run. weectl report run uses a dummy engine that loads all services as per weewx.conf, but never actually 'runs' the engine, so the loaded services don't actually do anything. Sure, you could have the dummy engine not load a few services to save a few bytes and microseconds, but since weectl report run is run and done in a few seconds it sounds like added complexity for little to no benefit.

R

--

You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/47da38da-dc64-4318-9fdc-0567e27e2bc0n%40googlegroups.com.