1
81%
master: 81%

Ran 04 Sep 2019 02:15PM UTC

Files 146

Run time 23s

Badge

Embed ▾

Committed 04 Sep 2019 02:10PM UTC coverage: 35.091%. Remained the same

Job # COMMAND="install"

Build Type

push

travis-ci

Committed by

jaimeperez

Commit Message

Make sure expired data is actually purged

The SimpleSAML\Session::expireData() method did not mark the session as dirty when there was expired data on it, so if nothing else changed, the data was never actually purged. It was done like this by design, but in practice, it seems like sessions aren't modified as often, meaning they end up growing a lot with each state array that's stored on them, and expired data is never removed. We now check for expired data in the save() method (which is run every time a session is destroyed, if not manually) and if there is any, we mark the session as dirty, so that it is actually updated in the backend. Most of the time this will be transparent and have no visible performance hit, as it'll be run after the response is sent, during shutdown.

This closes #1053

Run Details

4359 of 12422 relevant lines covered (35.09%)

2.1 hits per line

simplesamlphp / simplesamlphp / 4534 / 1
81%
master: 81%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 4534.1 (COMMAND="install")

simplesamlphp / simplesamlphp / 4534 / 1 81% master: 81%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 4534.1 (COMMAND="install")

simplesamlphp / simplesamlphp / 4534 / 1
81%
master: 81%

README BADGES
x