Some rows have backfilled times that are duplicates, causing the join to
join multiple rows. Assume ids only increment and fetch the row with the
highest id instead, and join on id.
This world type is not specifically a PVP world type; at the time of
this commit, world 365 is a non-PVP high-risk world, where the world is
the same as a regular members' world, except that the Protect Item
prayer is disabled.
- Remove spring boot test (no longer necessary)
- Move test development configuration to main package
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
This is a much more natural fit for the config service which is really a
key value store, and has been abusing SQL. This will let us expand the
config stuff later to support profiles and per-account config values.
I have left in the SQL code for now so config changes are still being
sent there in the event of catastrophic mongodb failure.
Instead of replacing configuration with test configuration on classpath,
create test profile and use that.
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
- Instead of replacing configuration with dev configuration on classpath,
create dev profile and use that
- Move common properties to application.yaml
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
The exclude is supposed to be on SpringBootApplication annotation,
otherwise IntelliJ Spring plugin errors, and also SpringBootApplication
already contains EnableAutoConfiguration.
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
The previous change to try and force GSON for serialization broke
default message converters such as text/plain. Change to use
extendMessageConverters and remove the Jackson converter instead.
This fixes deserailization of the loot timestamps for the loot tracker,
and maybe other things. Note this does not use the same Gson instance as
http-api as Spring creates its own Gson, however they are both default
Gson instances.
It is not very useful exception and cache entry is null-checked
everywhere else. Replace the exception with simple warning in logs.
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
Seeing same exceptions over and over again is not very useful, mainly
when their stacktraces are not useful too.
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
Use player rank to set how often the same player is allowed to be looked
up. Replace the ConcurrentLinkedDeque with a synchronized ArrayDeque
which has a constant time size().
Robert Alexander