DonationCoder.com Software > Find And Run Robot

User Variable value limit and Timer plugin problem

(1/2) > >>

skajfes:
I noticed that the user variable value length is limited to 1024 characters. It is not a problem in itself, but it causes the Timer plugin to stop working when you have enough timers in the history.

This is probably not so much a FARR core issue, as it is the Timer plugin issue.

Quick fix is to set the timer::archive uservalue to an empty array, but it would be great if the plugin could handle this automagically.

ewemoa:
Hmm...I wonder if this could be a contributing factor to the Timer plugin issue mentioned at:

  https://www.donationcoder.com/forum/index.php?topic=23406.0

May be it is possible for the Timer plugin to check what the length of the representation of the data is before trying to store the data.

ewemoa:
Tried making many timers and succeeded in causing a problem at FARR start up.

Also tried making a timer with an associated message which was waaaaaay too long and AFAICT this also caused a FARR start up problem.

Also was able to edit FindAndRunRobot.ini appropriately to get FARR to start again without reporting an error.  As one might guess, limited deletion (presumable to get the length of an appropriate user variable under some length) was sufficient.

Armando:
Do you guys get the JSON parser error I was getting?

skajfes:
I got the same error, yes. The Timer plugin stores it's past alarms as a JSON array in the user variable. FARR (or something else) limits the length of the value field to 1024 chars. When the array became longer than 1024 characters, everything that was behind the 1024th char was discarded. JSON string then became syntactically incorrect and caused the JSON parser error.

Navigation

[0] Message Index

[#] Next page