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

[PATCHv1 0/1] git-p4: better error reporting

From
Luke Diamand <luke@diamand.org>
Date
Jun 5, 2018, 08:55 UTC
Message-ID
<20180605085524.10838-1-luke@diamand.org>

If git-p4 cannot talk to the Perforce server, it will either give a confusing error message, or just crash. Even I get tripped up by this.

This change just checks that the client can talk to the server, and in particular that the user is logged in (the default login timeout is 12 hours).

It would be nice to also check for ticket expiration during long Perforce operations, but this change does not attempt to do that.

Luke Diamand (1):
  git-p4: better error reporting when p4 fails
 git-p4.py         | 55 +++++++++++++++++++++++++++++++++
 t/t9833-errors.sh | 78 +++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 133 insertions(+)
 create mode 100755 t/t9833-errors.sh
-- 
2.17.0.392.gdeb1a6e9b7
Next: Luke Diamand
Message 1 of 4 in “[PATCHv1 0/1] git-p4: better error reporting”
  1. Luke DiamandJun 5, 2018
  2. 1/1 git-p4: better error reporting when p4 failsLuke Diamand, Jun 5, 2018
  3. Luke DiamandJun 5, 2018
  4. Eric SunshineJun 5, 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.