{
  "WorkItem": {
    "AffectedComponent": {
      "Name": "",
      "DisplayName": ""
    },
    "ClosedComment": "fixed in changeset 32067.  First avail in v1.8.3.11",
    "ClosedDate": "2009-05-26T12:27:55.36-07:00",
    "CommentCount": 0,
    "Custom": null,
    "Description": "The only way a CRC checksum can be written to a stream is via the Close method.  Since the Close method swallows IO.IOException exceptions, it might swallow a hard-drive-full exception, or other exception when writing the CRC checksum.  Also, if the underlying stream was a custom stream, there might be other exceptions that would not be swallowed.  This could lead to faulty data streams being written when the code does not throw any exceptions.\n \nI suggest not swallowing exceptions, so that callers know if their streams are wrtten properly.  Since finalizers cannot call Close, it is not an issue.  Otherwise, I would add a EndFlush method to flush and end the stream, writing the CRC value (if necessary), and modify the Close method to swallow all exceptions.",
    "LastUpdatedDate": "2013-05-16T05:32:21.503-07:00",
    "PlannedForRelease": "",
    "ReleaseVisibleToPublic": false,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "DotNetZip",
    "ReportedDate": "2009-05-26T10:38:13.497-07:00",
    "Status": {
      "Name": "Closed",
      "Id": 4
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "1.8.3.9 - ZlibBaseStream.Close swallows IO exceptions",
    "Type": {
      "Name": "Issue",
      "Id": 3
    },
    "VoteCount": 1,
    "Id": 7814
  },
  "FileAttachments": [],
  "Comments": []
}