)]}'
{
  "commit": "b7fb2194b96604898ff1ddd8dd1a394aa71532a9",
  "tree": "e543ddaa13c3e685dfced61cdb37163c43058f72",
  "parents": [
    "81f86aacc4eb74cdb9c2c8082d36d2070c666045"
  ],
  "author": {
    "name": "Patrick Steinhardt",
    "email": "ps@pks.im",
    "time": "Thu Oct 23 09:14:59 2025 +0200"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Oct 23 09:52:55 2025 -0700"
  },
  "message": "t7528: work around ETOOMANY in OpenSSH 10.1 and newer\n\nIn t7528 we spawn an SSH agent to verify that we can sign a commit via\nit. This test has started to fail on some machines:\n\n    +++ ssh-agent\n    unix_listener_tmp: path \"/home/pks/Development/git/build/test-output/trash directory.t7528-signed-commit-ssh/.ssh/agent/s.UTulegefEg.agent.UrPHumMXPq\" too long for Unix domain socket\n    main: Couldn\u0027t prepare agent socket\n\nAs it turns out this is caused by a change in OpenSSH 10.1 [1]:\n\n * ssh-agent(1), sshd(8): move agent listener sockets from /tmp to\n   under ~/.ssh/agent for both ssh-agent(1) and forwarded sockets\n   in sshd(8).\n\nInstead of creating the socket in \"/tmp\", OpenSSH now creates the socket\nin our home directory. And as the home directory gets modified to be\nlocated in our test output directory we end up with paths that are\nsomewhat long. But Linux has a rather short limit of 108 characters for\nsocket paths, and other systems have even lower limits, so it is very\neasy now to exceed the limit and run into the above error.\n\nWork around the issue by using `ssh-agent -T`, which instructs it to\nuse the old behaviour and create the socket in \"/tmp\" again. This switch\nhas only been introduced with 10.1 though, so for older versions we have\nto fall back to not using it. That\u0027s fine though, as older versions know\nto put the socket into \"/tmp\" already.\n\nAn alternative approach would be to abbreviate the socket name itself so\nthat we create it as e.g. \"sshsock\" in the trash directory. But taking\nthe above example we\u0027d still end up with a path that is 91 characters\nlong. So we wouldn\u0027t really have a lot of headroom, and it is quite\nlikely that some developers would see the issue on their machines.\n\n[1]: https://www.openssh.com/txt/release-10.1\n\nReported-by: Xi Ruoyao \u003cxry111@xry111.site\u003e\nSuggested-by: brian m. carlson \u003csandals@crustytoothpaste.net\u003e\nHelped-by: Jeff King \u003cpeff@peff.net\u003e\nHelped-by: Lauri Tirkkonen \u003clauri@hacktheplanet.fi\u003e\nSigned-off-by: Patrick Steinhardt \u003cps@pks.im\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0f887a3ebee19b08e2bf7d9aa8ee74d7c4dbe177",
      "old_mode": 33261,
      "old_path": "t/t7528-signed-commit-ssh.sh",
      "new_id": "b50306b9b3952de838b20ccdf0f7ada865efd116",
      "new_mode": 33261,
      "new_path": "t/t7528-signed-commit-ssh.sh"
    }
  ]
}