shogi-server

Fork

Merge branch '201512-leastdiff'

[shogi-server] shogi_server/pairing.rb: Attempt more trials

LeastDiff attempts more trials, depending of a number of players to be matched.

Merge branch '201512-maxmoves'

[shogi-server] Enhance capability of Floodgate configuration file

- New parameter: Max_Moves, defined in the CSA protocol
ex. set Max_Moves 256
- New parameter: Least_Time_Per_Move, defined in the CSA protocol
ex. set Least_Time_Per_Move 0
- Proposed messages distributed to each player upon starting a new
game will include Max_Moves as well as Least_Time_Per_Move.
- CSA files produced by the server will include settings of
Max_Moves and Least_Time_Per_Move in comment lines as follows:
'Max_Moves:256
'Least_Time_Per_Move:0
- The official Shogi-server on wdoor.c.u-tokyo.ac.jp will
be running with different parameters, depending on game names.
a) Max_Moves will be 256 for floodgate-600-10 games;
otherwise, 0.
b) Least_Time_Per_Move will be 0 for floodgate-600-10 games;
otherwise 1.
(Closes: #35839)

Merge branch '201512-timeclock'

Fix #35795: A time consumed could be -1

* [shogi-server] shogi_server/time_clock.rb:
- A time consumed could be -1.
* The start time of a move is captured after sending a move to a
player of the next turn at the end of the giant lock
* The end time of the move is captured at the exact time when the
server receives it before the giant lock
Therefore, end_time < start_time is possible when a player returns a
move instantly.
Thanks to Tomoyuki Kaneko for reporting this issue.
(Closes: #35795)

util/statistics.rb: Updated to investigate floodgate-600-10 games.

Adjust sleep intervals to get more stable test results

[shogi-server] - shogi_server/login.rb: When players are logged in, log their player_id if they have it.

Update the revision

[mk_html] Links to details pages for players now use a relative path so that it works on a testing site.

Getting an absolute location of this file was wrong if it was a synbolic link. This issue has been addressed.

Merge branch 'wdoor-stable'

Conflicts:
changelog

Merge remote-tracking branch 'origin/wdoor-stable' into wdoor-stable

Conflicts:
changelog

[shogi-server] shogi-server, shogi_server/{command,game_result,player}.rb: The change at 2014-10-13 was not worked as expected. Reworked.

A player, attempting to login with the current live player
stalling for more than a day, can forcibly override the current
player.

Merge branch '201410-maxmoves'

Conflicts:
changelog
shogi_server.rb

Update various documentations

Fix test failures related to MAX_MOVES and least time per move

Apply CSA Protocol V1.2.1 for MAX_MOVES

Refactor ChessClockWithLeastZero

Corrected a changelog entry

Follow an API change in the upstream: LogDevice

Get rid of a dupolicated method: test_kachi_good

Fixed logout in test/TC_forrk.rb

New feature: Zero least time per move.

New command line option: --least-time-per-move n

Merge branch 'wdoor-stable'

Conflicts:
changelog

Merge remote-tracking branch 'origin/wdoor-stable' into wdoor-stable

Conflicts:
changelog

* [mk_html] Corrected a url.

* [shogi-server] When a non-rated player participates in Floodgate, the following exception was thrown and a Floodgate game would not start:

undefined method `[]' for nil:NilClass
["/home/shogi-server/www/x/shogi_server/pairing.rb:499:in `block
in calculate_diff_with_penalty'"

This issue has been resolved. Only players who have player ID
(i.e. those who log in with valid password) are now allowed to
participate in Floodgate as the spec web page
[http://shogi-server.sourceforge.jp/rating.html] describes.

[shogi-server] Addressed Ruby incompatibility on ShogiServer::Usi::alphabetToDan.

It (and usiToCsa.rb) did not work with Ruby 1.9.3. This issue has now been fixed.
Thanks to Hiraoka-san for debugging.