Skip to content

Conversation

@blizzz
Copy link
Member

@blizzz blizzz commented Jan 26, 2018

I am not aware this ever happened, but it does not need to.

Scenario: user exists check: when the LDAP server goes offline in the right moment, the user will be set as non-existing (for as long as cache lives), because any Exceptions was caught and ignored. We make sure to pass on ServerNotAvailable now.

might cause the user to be unavailable (race condition).

Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
Copy link
Member

@rullzer rullzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense!

@codecov
Copy link

codecov bot commented Jan 26, 2018

Codecov Report

Merging #8069 into master will increase coverage by <.01%.
The diff coverage is 50%.

@@             Coverage Diff              @@
##             master    #8069      +/-   ##
============================================
+ Coverage      51.7%   51.71%   +<.01%     
- Complexity    25456    25457       +1     
============================================
  Files          1599     1599              
  Lines         95275    95277       +2     
  Branches       1376     1376              
============================================
+ Hits          49266    49268       +2     
  Misses        46009    46009
Impacted Files Coverage Δ Complexity Δ
apps/user_ldap/lib/Access.php 35.77% <ø> (ø) 321 <0> (ø) ⬇️
apps/user_ldap/lib/User_LDAP.php 77.61% <50%> (-0.59%) 84 <0> (+1)
apps/files_trashbin/lib/Trashbin.php 72.53% <0%> (+0.24%) 136% <0%> (ø) ⬇️
lib/private/Files/Cache/Propagator.php 96.2% <0%> (+1.26%) 16% <0%> (ø) ⬇️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants