Hello Wilfred!

Friday June 02 2023 10:48, you wrote to Vince Coen:

Hi Vince,

On 2023-06-01 22:30:01, Elistmaint wrote to Mike Powell:

Echo Successfully Updated.

EL210 ==> Rules file WEATHER.TROPIC.RUL has been Updated.

TAGname: WEATHER.TROPIC Group: FIDO

TITLe: International Tropical/High Seas Weather Alerts

Language: ENGLISH

DESCription:
This echo is a companion to the Z1 WEATHER echo.
This echo contains tropical weather advisories for the
Atlantic
Pacific, and Indian Oceans, as well as high seas forcasts/
advisories. Discussion of tropical systems is also on-topic
and encouraged.

In the latest ELIST.RPT it says:

DESCription:

THERE IS NO DESCRIPTION ON FILE FOR THIS ECHO <<

For this area?

Thanks for the bug report.
I cannot see what is causing this as I have re-submitted the UPD file and it works.

I have made some changes to the code including changing these code blocks that are in paragraphs that are performed into sections that are performed - this will stop the risk of code full throughs, but cannot see how it will fix it.

Now looked at the log file and it shows it was deleted during the Warning run where it produces messages if any echo is or has expired so this is the next area to look at as there was 3 echos removed from the ELIST system.


Yes clutching at straws :(

S/w revised to v5.4.025 so now see if it happens again.

More later, may be.

Possible bug in the Warning routine as it deleted the three areas that has only
JUST gone beyond 10 months, looking.

Found it - had a end of routine period at end if an IF test when it should have
had a END-IF cluase.

Now to reinstate the three Echo's that was deleted :
HOROSCOPE, GUNS_N_SUCH and HOME_N_GRDN.

Just have to find the original submission files.

Thanks for the heads up.

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

Hi Vincent,

On 2023-08-02 16:12:32, you wrote to me:

In the ELIST.RPT for this month it is shown as:

DESCription:

THERE IS NO DESCRIPTION ON FILE FOR THIS ECHO <<

In the previous edition it was ok...

Update rerun and seems to be correct.

I have no idea why this happened for this area as the other updates appears
to be ok - unless you know different.

I didn't notice anything.

Please advise if you find any other oddities.

Will do. But you could use for instance https://winmerge.org/ (like I do) before you publish. It takes like 1 minute to do a side by side compare between the previous and latest versions, and spot these differences quite easily! ;-)

I seem to recall this has happened in the past for THIS echo, most
odd.

Your memory is correct. It happend 2 months ago for this same area...

@Mike Powell, if you are reading this pls change the volume to what is actual occurring for the echo as I find it very hard to take that
1,500 per month is any where near actual count on any fido echo let
alone this one.

If there are 5 weather reports for 10 locations a day, this could be a realistic number. Personally I don't see the need for these kinds of areas. If I want to know the weather for any place on earth I just look on the web for up to date information...

Bye, Wilfred.

--- FMail-lnx64 2.2.0.0
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

Wednesday August 02 2023 08:35, you wrote to me:

Hi Vincent,

On 2023-08-01 16:30:01, you wrote to Mike Powell:

Echo Successfully Updated.

EL210 ==> Rules file WEATHER.TROPIC.RUL has been Updated.

TAGname: WEATHER.TROPIC Group: FIDO

TITLe: International Tropical/High Seas Weather Alerts

Language: ENGLISH

DESCription:
This echo is a companion to the Z1 WEATHER echo.
This echo contains tropical weather advisories for the
Atlantic
Pacific, and Indian Oceans, as well as high seas forcasts/
advisories. Discussion of tropical systems is also on-topic
and encouraged.

In the ELIST.RPT for this month it is shown as:

DESCription:

THERE IS NO DESCRIPTION ON FILE FOR THIS ECHO <<

In the previous edition it was ok...

Update rerun and seems to be correct.

I have no idea why this happened for this area as the other updates appears to be ok - unless you know different.

Please advise if you find any other oddities.

Annoyingly, if it happens again I will have to rebuild the program to produce full run time trace that will show the code executed to see if the issue can be
located although it will be a right pain to trace the actual code for THAT specific echo other than by counting. Tracing produces a lot of output.

I seem to recall this has happened in the past for THIS echo, most odd.

Looking at the submission file the only may be oddities are it has mod and comod with email addresses but nothing that looks wrong, volume that is very high but cannot test it as it one of the few echos that I am not getting - possibly because of zero traffic as I cleared out last year a lot of dead
wood. Needless to say that could not be a logical reason for the issue as elist
does not check volume against actual, although early on it did but was presenting possible problems if my system was losing any traffic (unlikely but possible). Yet another feature that was removed as unneeded but may be nice to have.

@Mike Powell, if you are reading this pls change the volume to what is actual occurring for the echo as I find it very hard to take that 1,500 per month is any where near actual count on any fido echo let alone this one.

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8.3/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)