nicer message about MemoryError when eg unable to commit large files
Bug #109115 reported by
Martin Pool
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Medium
|
Martin Pool | ||
Bug Description
Until bug 109114 is fixed (to let you commit multi-gb files) it would be nice if Bazaar at least gave a clean message when large files can't be committed. This could be done by either
- catching MemoryError when the file is read -- though this still leaves some risk that we will be able to bring the file in, but will then fail on the next operation that allocates a byte of memory
- imposing some hardcoded limit, say 100MB, that should be large enough for source code but small enough to fit into vm on even small machines.
Related branches
| Changed in bzr: | |
| importance: | Undecided → Medium |
| status: | Unconfirmed → Confirmed |
| Changed in bzr: | |
| assignee: | nobody → Martin Pool (mbp) |
| status: | Confirmed → In Progress |
Revision history for this message
| Martin Pool (mbp) wrote Re: nicer error when unable to commit large files | #1 |
| Changed in bzr: | |
| status: | In Progress → Fix Committed |
| summary: |
- nicer error when unable to commit large files + nicer message about MemoryError when eg unable to commit large files |
| Changed in bzr: | |
| status: | Fix Committed → Fix Released |
| milestone: | none → 2.1 |
| Changed in bzr: | |
| milestone: | 2.1.0 → 2.1b1 |
To post a comment you must log in.
mp https:/