git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCHv2 5/6] git-p4: narrow the scope of exceptions caught when parsing an int

From
Luke Diamand <luke@diamand.org>
Date
Jun 8, 2018, 20:32 UTC
Message-ID
<20180608203248.16311-6-luke@diamand.org>
In-Reply-To
<20180608203248.16311-5-luke@diamand.org>

The current code traps all exceptions around some code which parses an integer, and then talks to Perforce.

That can result in errors from Perforce being ignored. Change the code to only catch the integer conversion exceptions.

Signed-off-by: Luke Diamand <luke@diamand.org>
---
 git-p4.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/git-p4.py b/git-p4.py
index f4b5deeb83..5f59feb5bb 100755
--- a/git-p4.py
+++ b/git-p4.py
@@ -959,7 +959,7 @@ def p4ChangesForPaths(depotPaths, changeRange, requestedBlockSize):
         try:
             (changeStart, changeEnd) = p4ParseNumericChangeRange(parts)
             block_size = chooseBlockSize(requestedBlockSize)
-        except:
+        except ValueError:
             changeStart = parts[0][1:]
             changeEnd = parts[1]
             if requestedBlockSize:
-- 
2.17.0.392.gdeb1a6e9b7
Previous: Luke DiamandNext: Luke Diamand
Message 6 of 13 in “[PATCHv2 0/6] git-p4: some small fixes updated”
  1. Luke DiamandJun 8, 2018
  2. 1/6 git-p4: disable-rebase: allow setting this via configurationLuke Diamand, Jun 8, 2018
  3. 2/6 git-p4: add option to disable syncing of p4/master with p4Luke Diamand, Jun 8, 2018
  4. 3/6 git-p4: better error reporting when p4 failsLuke Diamand, Jun 8, 2018
  5. 4/6 git-p4: raise exceptions from p4CmdList based on error from p4 serverLuke Diamand, Jun 8, 2018
  6. 5/6 git-p4: narrow the scope of exceptions caught when parsing an intLuke Diamand, Jun 8, 2018
  7. 6/6 git-p4: auto-size the blockLuke Diamand, Jun 8, 2018
  8. Junio C HamanoJun 12, 2018
  9. Luke DiamandJun 12, 2018
  10. Junio C HamanoJun 12, 2018
  11. Luke DiamandJun 12, 2018
  12. Eric SunshineJun 12, 2018
  13. Luke DiamandJun 12, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.