github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-14 03:46:23 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

PANIC 'runtime error: index out of range' on pull request #2136

New Issue
Closed
opened 2025-11-02 04:25:06 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 04:25:06 -06:00
Owner
Copy Link

Originally created by @nuno-silva on GitHub (Aug 3, 2018).

Description

I was editing a comment on a pull request. When I tried to submit the comment, I got an internal server error. Since then, the page for this pull request always fails with runtime error: index out of range. Other pages in gitea work.

I remember starting time tracking while editing the comment.

I couldn't reproduce the error in try.gitea.io so far.

Any pointers on where to start debugging the error would be appreciated.
...

Screenshots

Originally created by @nuno-silva on GitHub (Aug 3, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.4.3 - Git version: 2.16.4 - Operating system: Gentoo Linux - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: https://gist.github.com/nuno-silva/5bef3d8dd47523a1ed7d461349f34a9f ## Description I was editing a comment on a pull request. When I tried to submit the comment, I got an internal server error. Since then, the page for this pull request always fails with `runtime error: index out of range`. Other pages in gitea work. I remember starting time tracking while editing the comment. I couldn't reproduce the error in try.gitea.io so far. Any pointers on where to start debugging the error would be appreciated. ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror commented 2025-11-02 04:25:07 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 3, 2018):

@nuno-silva could you upgrade to v1.4.3 and confirm the bug is still there?

@lunny commented on GitHub (Aug 3, 2018): @nuno-silva could you upgrade to v1.4.3 and confirm the bug is still there?
GiteaMirror commented 2025-11-02 04:25:07 -06:00
Author
Owner
Copy Link

@nuno-silva commented on GitHub (Aug 3, 2018):

@lunny the error is still happening on v1.4.3. I've updated the gist and issue description.

@nuno-silva commented on GitHub (Aug 3, 2018): @lunny the error is still happening on v1.4.3. I've updated the gist and issue description.
GiteaMirror commented 2025-11-02 04:25:07 -06:00
Author
Owner
Copy Link

@nuno-silva commented on GitHub (Aug 3, 2018):

@lunny I was able to reproduce the bug again in v1.4.3.

Simply opening a new issue and writing either of these in a comment triggers an internal error:

[[https://www.freedesktop.org/software/systemd/man/networkd.conf.html#DUIDType=]]

[[=]]

In try.gitea.io (9c354a5), the rendered comment is empty, but does NOT trigger an internal error:
https://try.gitea.io/nuno-silva/test/issues/3

@nuno-silva commented on GitHub (Aug 3, 2018): @lunny I was able to reproduce the bug again in v1.4.3. Simply opening a new issue and writing either of these in a comment triggers an internal error: ``` [[https://www.freedesktop.org/software/systemd/man/networkd.conf.html#DUIDType=]] ``` ``` [[=]] ``` In try.gitea.io (9c354a5), the rendered comment is empty, but does NOT trigger an internal error: https://try.gitea.io/nuno-silva/test/issues/3
GiteaMirror commented 2025-11-02 04:25:07 -06:00
Author
Owner
Copy Link

@nuno-silva commented on GitHub (Aug 3, 2018):

As a workaround, I altered the affected comment's content in the database:

update comment set content="workaround" where issue_id=504 and id=1392;
@nuno-silva commented on GitHub (Aug 3, 2018): As a workaround, I altered the affected comment's content in the database: ``` update comment set content="workaround" where issue_id=504 and id=1392; ```
GiteaMirror commented 2025-11-02 04:25:07 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 6, 2018):

It seems master have fixed that issue.

@lunny commented on GitHub (Aug 6, 2018): It seems `master` have fixed that issue.
GiteaMirror commented 2025-11-02 04:25:08 -06:00
Author
Owner
Copy Link

@nuno-silva commented on GitHub (Aug 6, 2018):

Yes. [[=]] seems to be invalid markdown anyway, so as long as it doesn't crash I think it's acceptable behaviour.
Reopen if you disagree.

@nuno-silva commented on GitHub (Aug 6, 2018): Yes. `[[=]]` seems to be invalid markdown anyway, so as long as it doesn't crash I think it's acceptable behaviour. Reopen if you disagree.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2136
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?