From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from secure.elehost.com (secure.elehost.com [185.209.179.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6D2EB3491F6 for ; Fri, 24 Oct 2025 18:38:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.209.179.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761331096; cv=none; b=NqJ5pGps/Y8ue54TBoPskehxEl5j7XRaZrgZFB2bvmMCHNUb992s8vmUs9mCgnMhJS1diVAe9TUc4xCSiHsW52KTP+GR/hkTE8oD/ccZqgn5k1vy0ePY+hzCooJpn8RJafR0D7q8W1cWNMvC9r7zDHyB8Q7kBz4/TIZTu2M1sJs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761331096; c=relaxed/simple; bh=OkyZ+BGbPe5bj9crN+y+aZbtE96DOQJIOT5lX1Gak3E=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=OrvNVEYeqNOJIexG9CcrGHSOVPlozVd36yNelwlqlKml9Q3Z921UjiUwKODPR4LD9hbJt1g9ObWxiFgDzR66ONkYaQSVLnptURYomSTokBGTAB59clD2u0Fr6/5ybFAd5GydirR8I44GkI0lgW1bYWiARyrmsWfi5ofRf60eeRY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=nexbridge.com; spf=pass smtp.mailfrom=nexbridge.com; arc=none smtp.client-ip=185.209.179.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=nexbridge.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=nexbridge.com X-Virus-Scanned: Debian amavisd-new at secure.elehost.com Received: from Mazikeen (pool-99-228-67-183.cpe.net.cable.rogers.com [99.228.67.183]) (authenticated bits=0) by secure.elehost.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 59OIcABG798059 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 24 Oct 2025 18:38:11 GMT Reply-To: From: To: "'Jeff King'" Cc: "'D. Ben Knoble'" , References: <012601dc42ce$a1adcb50$e50961f0$@nexbridge.com> <013201dc42d5$07a71550$16f53ff0$@nexbridge.com> <20251022092708.GE853931@coredump.intra.peff.net> <018701dc435f$f1dc1a00$d5944e00$@nexbridge.com> <20251023124837.GB1163932@coredump.intra.peff.net> <029a01dc450c$4318dfe0$c94a9fa0$@nexbridge.com> <20251024174659.GA3635620@coredump.intra.peff.net> In-Reply-To: <20251024174659.GA3635620@coredump.intra.peff.net> Subject: RE: [BUG] Strange git notes completion behaviour Date: Fri, 24 Oct 2025 14:38:05 -0400 Organization: Nexbridge Inc. Message-ID: <029f01dc4515$59ae09c0$0d0a1d40$@nexbridge.com> Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Content-Language: en-ca Thread-Index: AQHjmO9AERlM/1ZhxKXB7Q1XH17MtgEgLITOApwjn/kCVAmtvwG1oGkTAur+K2wCggldTgJg/ggBtEZYi6A= X-Antivirus: Norton (VPS 251024-10, 10/24/2025), Outbound message X-Antivirus-Status: Clean On October 24, 2025 1:47 PM, Jeff King wrote: >On Fri, Oct 24, 2025 at 01:33:02PM -0400, rsbecker@nexbridge.com wrote: > >> What I found is this: >> >> Git drops into sane_execvp and converts the >> >> git notes show HEAD >> >> to >> >> git show 1aa950256829721750e809788e7b858db79a934a. >> >> When execvp is called, it immediately fails with a -12 - not = returned, >> just terminates. The -12 is an NonStop-specific execvp error >> indicating the process failed because the object is invalid (strange >> and likely an artifact rather than a real problem). > >When you say "object" here, you don't mean a Git object, but rather = that >execvp() could not run the "git" binary for some reason (so the = "object" >here is the on-disk executable)? Just making sure I understand. > >> When I use the arguments as presented to execvp via bash directly, I = get: >> >> error: no note found for object >1aa950256829721750e809788e7b858db79a934a. >> >> There is no commit with that hash. HEAD is actually >> 3fc1917e0e69b23265f5c49f90fdb6f4ed98f4a3 >> so git show is correctly failing. This is Indicating that notes is = not >> invoking git correctly. > >Are you sure you are running "git show" there and not "git notes show". >Because 1aa950256 should be the blob that the note for HEAD points to, = and thus >does not itself have a note. And "git show" should not be looking up = notes at all >(and the "no note found" message is from builtin/notes.c). I am 100% sure that git notes show is running git show with the notes = blob as above.