Actions
Bug #125
closedWe should return the error code on time limit exeeded
Status:
Rejected
Priority:
5 (lowest)
Assignee:
-
Category:
Architecture - Internal libs
Target version:
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.
Updated by François ARMAND almost 15 years ago
- Priority changed from 4 to 5 (lowest)
Change priority
Updated by François ARMAND almost 14 years ago
- Tracker changed from User story to Bug
- Project changed from 9 to 18
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 24 to 18
Updated by François ARMAND over 12 years ago
- Target version changed from 18 to 24
Updated by François ARMAND almost 12 years ago
- Target version changed from 24 to Ideas (not version specific)
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 18 to Rudder
- Category set to Architecture - Internal libs
Updated by François ARMAND over 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