The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
See attached lwpset.txt for details on cleanups needed.
BugTraq+ Release Management Values
COMMIT TO FIX:
(Copied from evaluation of 4810500)
The majority of these cleanups are needed. We need a better model
for providing informational printouts to customers than yet another
flag here. For the initial bug reported, it is worth returning
EAGAIN, OR putting a small retry logic in right here. It might
make more sense to turn this into an assertion for debug time.
While this is hard to duplicate it would be valuable to understand
why it failed and if it is ever the case that retrying could succeed.
Definately worth a small email proposal for fixes prior to implementing.
The suggested cleanups The cleanups suggested by Dave Dice have been implemented. The assertion checking has been moved to the debug VM
and the UseThreadPriorities flag has been used to guard all priority