From: "transient@anthonyv.be" <transient@anthonyv.be>
To: git@vger.kernel.org
Subject: Bug report: gitk is unable to handle OpenJDK repository
Date: Thu, 25 Mar 2021 17:57:46 +0100 [thread overview]
Message-ID: <5085-605cc100-dd-414bfa80@70853048> (raw)
What did you do before the bug happened? (Steps to reproduce your issue)
Clone https://github.com/openjdk/jdk
Launch gitk with `gitk --all` and wait for all commits to be read
Scroll down
What did you expect to happen? (Expected behavior)
Scrolling down, though possibly slow due to the large repository size, works as expected all the way back to the initial commit.
What happened instead? (Actual behavior)
At some point, the following error occurs and it's impossible to scroll neither up nor down without the error occuring.
The error is:
Error: expected integer but got ""
expected integer but got ""
expected integer but got ""
(reading increment)
invoked from within
"incr i [lindex $varcrow($v) $a]"
(procedure "rowofcommit" line 22)
invoked from within
"rowofcommit $id"
(procedure "nextuse" line 15)
invoked from within
"nextuse $p $r"
(procedure "make_idlist" line 23)
invoked from within
"make_idlist $row"
(procedure "layoutrows" line 21)
invoked from within
"layoutrows $rl1 $r"
(procedure "drawcommits" line 36)
invoked from within
"drawcommits $row $endrow"
(procedure "drawvisible" line 53)
invoked from within
"drawvisible"
(procedure "scrollcanv" line 3)
invoked from within
"scrollcanv .tf.histframe.csb 0.30222245490955735 0.3026978351352059"
What's different between what you expected and what actually happened?
The error occuring and the inability to recover from it.
[System Info]
git version: git version 2.30.2.windows.1
cpu: x86_64
built from commit: 37f0a4afad027cf030747a1ef45537ba86162960
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
uname: Windows 10.0 19042
compiler info: gnuc: 10.2
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>
[Enabled Hooks]
Kind regards,
Anthony
reply other threads:[~2021-03-25 16:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5085-605cc100-dd-414bfa80@70853048 \
--to=transient@anthonyv.be \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).