Cumulus Support

I guess Twitter can have problems occasionally, lol!
It's just a weird coincidence that, for the first time in at least 24 hours, I happen to look at my 15 minute CMX generated tweets and it shows...

4 x 5h ago
4 x 4h ago
4 x 3h ago
2 x 2h ago
58m ago
13m ago

...with no obvious local problem that would have affected CMX (WU graphs are ok). Strange.

Assuming that you have debug logging turned on, the diags file will show the Twitter updates and any replies.

Just check Debug logging in Options and there should be a file in Diags? There is nothing (I restarted CMX just in case).
There was no Logging=1 in the Station section of the ini so I added that and restarted CMX. Still no diags file.
I must be missing something, unless of course there are only diags if there is a problem.

The diags file for MX are in the MXdiags folder. It creates a new diags file every time it runs, and keeps the latest 10 (just like Cumulus 1).

Oh, lol! Stara chovek, losh pamet.

OK, are you inhibiting because it is over 140 characters or is Twitter? I figured it would just be truncated.

It appears that a valid one goes something like this...

2015-10-17 21:30:06.961 Starting Twitter update
2015-10-17 21:30:06.961 Using twitter.txt file
2015-10-17 21:30:06.961 Updating Twitter: Sunrise☼07:26/set✹18:25
Temp ҉ 12.7°C…Humidity ҈ 94%…Wind֍0.0km/h➤N…Rain░0.0mm…Barometer⇅1014.6hPa…Forecast ► Fine weather

2015-10-17 21:30:08.206 Status returned: (655450735900012544)[Jerbil's Weather]Jerbil's Weather, Sunrise☼07:26/set✹18:25
Temp ҉ 12.7°C…Humidity ҈ 94%…Wind֍0.0km/h➤N…Rain░0.0mm…Barometer⇅1014.6hPa…Forecast ► Fine weather, 17/10/2015 18:30:07

...and an invalid one looks like this...

2015-10-17 03:45:07.776 UpdateTwitter: Status is over 140 characters.

There is the odd forecast text that would take it over 140. If it is you (I guess it must be) can't you just truncate it?

It's not MX, the error is from Twitter itself. MX can't truncate it because it doesn't (reliably) know how long it actually will be by the time it is encoded and arrives at Twitter. When I get a minute, I'll have a look at the library I use to see if it offers any help with this.

Actually, the wiki says "If your eventual tweet is over 140 character it will be truncated by Cumulus."


...and why is there no...

date time Starting Twitter update
date time Using twitter.txt file

in the log, if it isn't you inhibiting it?

gluepack wrote:Actually, the wiki says "If your eventual tweet is over 140 character it will be truncated by Cumulus."

That's Cumulus 1. And I'm not sure that Cumulus 1 always gets it right anyway. Twitter is a huge pain in the arse.

...and why is there no...

date time Starting Twitter update
date time Using twitter.txt file

in the log, if it isn't you inhibiting it?

Because you didn't have debug logging turned on.

Sorry, you misunderstood but, anyway, I was wrong suggesting it was CMX that was inhibiting it for being over 140 because I just got a "duplicate" message in a similar format (without the "Starting..." and "Using..." messages) which, presumably, must have come from Twitter.

Anyway, I have modified the tweet so that it should now cater for about 35 characters for the forecast which should reduce the number of rejections.

Thanks