Ticket History #6047: NIM: kherr should keep track of first error instead of last

# Tue Jul 22 17:02:38 2008 asanka (asanka@mit.edu) - Ticket created

Subject:

NIM: kherr should keep track of first error instead of last

Download (untitled) / with headers
text/plain 770B

The NIM error reporting functions (in src/windows/identity/kherr ) keep
track of the the error message with the highest severity level that was
reported for a specific error reporting context. However, if another
error message of the same severity is reported, the error message being
tracked will be updated to be the newly received error.

The user will often only be notified of the error message that was
tracked for a specific operation. Therefore, tracking the last message
with the highest priority has the unfortunate side-effect of not
reporting the cause of a failure.

This patch changes the condition for updating the tracked error message
to be the first message with the highest severity.

Patch generated against /src/windows/identity in the SVN trunk.

Download nim-kherr-track-first-error-instead-of-last.patch
application/octet-stream 376B

Message body not shown because it is not plain text.

# Wed Jul 23 11:07:28 2008 jaltman (Jeffrey Altman) - Status changed from 'new' to 'open'

# Wed Jul 23 11:07:28 2008 jaltman (Jeffrey Altman) - Queue changed from kfw to krb5

# Wed Jul 23 11:08:28 2008 jaltman (Jeffrey Altman) - Component windows added

# Wed Jul 23 11:09:20 2008 jaltman (Jeffrey Altman) - Given to jaltman (Jeffrey Altman)

# Wed Jul 23 11:09:20 2008 jaltman (Jeffrey Altman) - Status changed from 'open' to 'review'

# Wed Jul 23 11:09:21 2008 jaltman (Jeffrey Altman) - Tags pullup added

# Wed Jul 23 11:09:21 2008 jaltman (Jeffrey Altman) - Correspondence added

From:	jaltman@mit.edu
Subject:	SVN Commit

Download (untitled) / with headers
text/plain 806B

The NIM error reporting functions (in src/windows/identity/kherr ) keep
track of the the error message with the highest severity level that was
reported for a specific error reporting context. However, if another
error message of the same severity is reported, the error message being
tracked will be updated to be the newly received error.

The user will often only be notified of the error message that was
tracked for a specific operation. Therefore, tracking the last message
with the highest priority has the unfortunate side-effect of not
reporting the cause of a failure.

This patch changes the condition for updating the tracked error message
to be the first message with the highest severity.

Commit By: jaltman

Revision: 20573
Changed Files:
U trunk/src/windows/identity/kherr/kherr.c

# Mon Aug 11 11:08:57 2008 tlyu (Taylor Yu) - Version_Fixed 1.6.4 added

# Mon Aug 11 11:08:57 2008 tlyu (Taylor Yu) - Correspondence added

From:	tlyu@mit.edu
Subject:	SVN Commit

Download (untitled) / with headers
text/plain 977B

pull up r20573 from trunk

r20573@cathode-dark-space: jaltman | 2008-07-23 11:09:15 -0400
ticket: 6047
tags: pullup

The NIM error reporting functions (in src/windows/identity/kherr ) keep
track of the the error message with the highest severity level that was
reported for a specific error reporting context. However, if another
error message of the same severity is reported, the error message being
tracked will be updated to be the newly received error.

The user will often only be notified of the error message that was
tracked for a specific operation. Therefore, tracking the last message
with the highest priority has the unfortunate side-effect of not
reporting the cause of a failure.

This patch changes the condition for updating the tracked error message
to be the first message with the highest severity.

Commit By: tlyu

Revision: 20641
Changed Files:
_U branches/krb5-1-6/
U branches/krb5-1-6/src/windows/identity/kherr/kherr.c

# Tue Aug 12 10:46:30 2008 tlyu (Taylor Yu) - Status changed from 'review' to 'resolved'

# Wed Dec 16 18:02:52 2015 tlyu (Taylor Yu) - CustomField pullup deleted