Evergreen

evergreen:tags/rel_2_12_10

  1. Git
  2. lp:evergreen
  3. tags/rel_2_12_10
Last commit made on 2018-02-21
Get this branch:
git clone -b tags/rel_2_12_10 https://git.launchpad.net/evergreen

Branch merges

Branch information

Name:
tags/rel_2_12_10
Repository:
lp:evergreen

Recent commits

c23bc26... by Blake GH on 2018-02-21

Bumping version numbers, adding Upgrade Script and Changelog

Signed-off-by: blake <email address hidden>

64cd9b2... by Blake GH on 2018-02-21

bumping Perl version string for 2.12.10

Signed-off-by: blake <email address hidden>

737f75f... by Blake GH on 2018-02-21

Translation updates - po files

Signed-off-by: blake <email address hidden>

70c3128... by Blake GH on 2018-02-21

cd build/i18n && make newpot

Signed-off-by: blake <email address hidden>

8c77532... by Jane Sandberg on 2018-02-20

Docs: fixing typo in 2.12.9 release notes

Signed-off-by: Jane Sandberg <email address hidden>

197aeae... by Jane Sandberg on 2018-02-20

Release notes for 2.12.10

Signed-off-by: Jane Sandberg <email address hidden>

9f63d10... by Dan Wells on 2018-02-20

LP#1749992 Disable payment button during payment

Since the display is not refreshed until the payment finishes, it
is possible to fire off a second payment by double-clicking.

This commit is a simple way to disable the button while a payment is
in process, then enable it again after the display refreshes.

Since the 'sendPayment()' function is wrapped, we may need to move
this logic up, but this being a single promise is simpler, and it
solved the problem in testing.

Signed-off-by: Dan Wells <email address hidden>
Signed-off-by: Jason Stephenson <email address hidden>

cf61fa0... by Galen Charlton on 2018-01-25

LP#1745486: avoid retrieving user by id::numeric during auth init

During open-ils.auth.authenticate.init, if looking up the user by barcode,
the actor.usr row is subsequently fetched by ID. However, the ID was
turned into a float, meaning that the query as sent to the database
was equivalent to

  SELECT * FROM actor.usr WHERE id = 123.0000;

While PostgreSQL will accept this, it ends up doing a sequential
scan of the actor.usr table rather than an index lookup, making the
retrieval up to two orders of magnitude slower than it needs to be
and adding a couple percent unecessary I/O load on large, heavily
used database. This patch fixes that.

To test
-------
[1] Turn on PostgreSQL statment logging and log in as a user
    by barcode. Note that there's a retrieval of actor.usr by
    a float form of the ID.
[2] Apply the patch and repeat step 1. This time, the query
    retrieves the row by the integer form of the ID.

Signed-off-by: Galen Charlton <email address hidden>
Signed-off-by: Bill Erickson <email address hidden>

84bb1f5... by Dan Wells on 2018-01-17

Forward port 2.12.9 upgrade script

Signed-off-by: Dan Wells <email address hidden>

4efc472... by Jane Sandberg on 2018-01-17

Release notes for 2.12.9

Signed-off-by: Jane Sandberg <email address hidden>