Project

General

Profile

Actions
Copy link

Bug #125

closed

We should return the error code on time limit exeeded

Added by François ARMAND about 14 years ago. Updated almost 8 years ago.

Status:
Rejected
Priority:
5
Assignee:
-
Category:
Architecture - Internal libs
Target version:
Ideas (not version specific)
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Now, we consider a time|size limit exeeded as success - obviously, it is not.
Think of a way to pass that information back from LdapConnection to higher level.

Actions
Copy link
 #1

Updated by François ARMAND about 14 years ago

  • Priority changed from 4 to 5

Change priority

Actions
Copy link
 #2

Updated by François ARMAND over 13 years ago

  • Tracker changed from User story to Bug
  • Project changed from 9 to 18
Actions
Copy link
 #3

Updated by François ARMAND over 12 years ago

  • Target version set to 24
Actions
Copy link
 #4

Updated by Jonathan CLARKE almost 12 years ago

  • Target version changed from 24 to 18
Actions
Copy link
 #5

Updated by François ARMAND over 11 years ago

  • Target version changed from 18 to 24
Actions
Copy link
 #6

Updated by François ARMAND about 11 years ago

  • Target version changed from 24 to Ideas (not version specific)
Actions
Copy link
 #7

Updated by Benoît PECCATTE about 9 years ago

  • Project changed from 18 to Rudder
  • Category set to Architecture - Internal libs
Actions
Copy link
 #8

Updated by François ARMAND almost 8 years ago

  • Status changed from New to Rejected

This is an internal pb. In real life, LDAP is never the bottleneck for that. And the proposed solution is not and actual solution (no better than having a log message at least).

Closing it.

Actions
Copy link

Also available in: Atom PDF