Test result on 3.23b

[Guido]

Hey Frylock, since I have no other way of contacting you atm; here we go. First of all, great updates, most of them did affect me in some way, and happy to see those fixed! Found two minor issues; no showstoppers:

!records 
-->results-->
2016-06-05 23:35:11,015 ERROR (CommandManager.java:run:134)
Command could not be handled: records
java.lang.IllegalArgumentException: String cannot be parsed: reply_message(5)<{}>
        at api.irc.communication.IRCMessageFactory.parseAndCreateNewMessages(IRCMessageFactory.java:156)
        at internal.templates.TemplateManagerImpl.processIRCView(TemplateManagerImpl.java:112)
        at internal.templates.TemplateManagerImpl.process(TemplateManagerImpl.java:83)
        at internal.templates.TemplateManagerImpl.createOutputFromTemplate(TemplateManagerImpl.java:73)
        at internal.commands.CommandManager.handleCommand(CommandManager.java:192)
        at internal.commands.CommandManager.access$400(CommandManager.java:76)
        at internal.commands.CommandManager$1$1.call(CommandManager.java:121)
        at internal.commands.CommandManager$1$1.call(CommandManager.java:113)
        at api.database.transactions.Transactions.inTransaction(Transactions.java:112)
        at api.database.transactions.Transactions.inTransaction(Transactions.java:91)
        at internal.commands.CommandManager$1.run(CommandManager.java:113)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)

Cause: No records recorded yet!
Are Records gonna be exposed via the API too? :)


-------------------------------------------------------------------------------------------------------------------------------

Api Documentation on /password/ :
[Query Param] userId (String) - The id or location of the kingdom to limit the results to --> location/kingdom on userId? :)

[Kyle]

Uploaded a fixed version for these items - thanks for testing.

So the records feature needs a few things:

1) API (alongside HoF, the destroyer of IRC line limits)

2) Ability to delete specific records

3) Be a part of reset for EOA.

I'm hoping to have these ready before year 9 so we can test a bit before EOA.

[Kyle]

Reminder to myself from IRC:

<Ex> Hey, just noticed, batch sending ops creates 1 total for Records. I.e. sending 5xsteal horses at 500 a pop creates a new Record for biggest Steal Horses @ 2,500 horses

[Kyle]

Resolved pretty much all of these in 794be50

[Guido]

Since this issue more or less acts like a notepad ...

You asked about the mariadb error wrt !armies. Yes, that causes the same sql error: http://pastebin.com/UgyZ6tKJ

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for
 the right syntax to use near ') and this_.type='IRC_ARMY_OUT' order by this_.returning_date asc' at line 1

[Kyle]

Moved the most recent comment to its own issue:

https://bitbucket.org/fredrik_yttergren/lucidbot/issues/32/bot-doesnt-play-well-with-maridb