{"version":"2.1.282","anchor":"transcript-line-reader-closes-file-handles-safely-and-gains","canonical_anchor":"transcript-line-reader-closes-file-handles-safely-and-gains","heading":"Transcript file reading keeps the real error when closing fails","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/transcript-line-reader-closes-file-handles-safely-and-gains","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Transcript file reading keeps the real error when closing fails\n\nReading transcript files now reports the original error even if closing the file also fails, and can read a chosen part of a file\n\n**Unclear.** Whether this has any effect a user would notice is not known.\n\n**What**\n\nThe code that reads session transcripts (the saved record of a conversation) can now read a specific part of a file directly, as well as the whole file. When an error happens and closing the file then fails too, the original error is kept instead of being replaced.\n\n**Why**\n\nThis is mostly reliability work. Error messages from reading transcripts are more likely to point at the real problem.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}