pcottle/learnGitBranching · info · CommandResult

bigLogStr

Error message

bigLogStr

What it means

Not a failure: logWithout builds output for 'git log <ref> ^<omitBranch>' by having RevisionRange.formatRevisions emit one commit id per line; the concatenated string is returned by throwing a CommandResult.

Source

Thrown at src/js/git/index.js:3136

    msg: msg
  });
};

GitEngine.prototype.logWithout = function(ref, omitBranch) {
  // slice off the ^branch
  omitBranch = omitBranch.slice(1);
  this.log(ref, Graph.getUpstreamSet(this, omitBranch));
};

GitEngine.prototype.revlist = function(refs) {
  var range = new RevisionRange(this, refs);

  // now go through and collect ids
  var bigLogStr = range.formatRevisions(function(c) {
    return c.id + '\n';
  });

  throw new CommandResult({
    msg: bigLogStr
  });
};

GitEngine.prototype.log = function(refs) {
  var range = new RevisionRange(this, refs);

  // now go through and collect logs
  var bigLogStr = range.formatRevisions(function(c) {
    return c.getLogEntry();
  });

  throw new CommandResult({
    msg: bigLogStr
  });
};

GitEngine.prototype.getCommonAncestor = function(ancestor, cousin, dontThrow) {

View on GitHub (pinned to 5b09d0ff96)

Solutions

  1. No fix needed
  2. Parse msg lines if you need the commit id list
Defensive patterns

Strategy: try-catch

Try / catch

try { engine.logWithout(ref, omit); } catch (e) { if (e instanceof CommandResult) { var ids = e.msg.trim().split('\n'); } else throw e; }

Prevention

When it happens

Trigger: Successful git log ref ^other execution; every revision in the range contributes 'id\n'.

Common situations: Normal usage; expected output.

Related errors


AI-assisted analysis of pcottle/learnGitBranching@5b09d0ff96 (2026-08-27). Data as JSON: /api/errors/da11e2e31b476a99. Report an issue: GitHub.