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

Gitea "InitIssuesIndexer, open index: incompatible version, 5 is supported" #1188

New Issue
Closed
opened 2025-11-02 03:51:49 -06:00 by GiteaMirror · 10 comments
GiteaMirror commented 2025-11-02 03:51:49 -06:00
Owner
Copy Link

Originally created by @ghost on GitHub (Oct 27, 2017).

Description

Gitea start error. Details in log file.

Originally created by @ghost on GitHub (Oct 27, 2017). - Gitea version (or commit ref): 1.2.2 - Git version: 2.7.4 - Operating system: Linux Mint - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: https://gist.github.com/ahme-t/03e24a734b1d6fdfc65d53f464d628ca ## Description Gitea start error. Details in log file.
GiteaMirror added the type/bug label 2025-11-02 03:51:49 -06:00
GiteaMirror commented 2025-11-02 03:51:50 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Oct 27, 2017):

You can just delete issue.bleve from indexers directory and it will be regenerated

@lafriks commented on GitHub (Oct 27, 2017): You can just delete issue.bleve from indexers directory and it will be regenerated
GiteaMirror commented 2025-11-02 03:51:50 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Oct 27, 2017):

I think this is fixed in master branch with #2524

@lafriks commented on GitHub (Oct 27, 2017): I think this is fixed in master branch with #2524
GiteaMirror commented 2025-11-02 03:51:50 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Oct 27, 2017):

@ethantkoenig can you backport it to 1.2?

@lafriks commented on GitHub (Oct 27, 2017): @ethantkoenig can you backport it to 1.2?
GiteaMirror commented 2025-11-02 03:51:50 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 27, 2017):

Thanks solved

@ghost commented on GitHub (Oct 27, 2017): Thanks solved
GiteaMirror commented 2025-11-02 03:51:50 -06:00
Author
Owner
Copy Link

@ethantkoenig commented on GitHub (Oct 27, 2017):

@lafriks That would require also backporting #2387.

FYI, this error can only happen when the bleve library is updated, so as long as we don't update bleve on the 1.2 release branch, this fix isn't strictly necessary

@ethantkoenig commented on GitHub (Oct 27, 2017): @lafriks That would require also backporting #2387. FYI, this error can only happen when the bleve library is updated, so as long as we don't update bleve on the 1.2 release branch, this fix isn't strictly necessary
GiteaMirror commented 2025-11-02 03:51:50 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Oct 27, 2017):

@ethantkoenig Could it be that bleve was updated between 1.1 and 1.2?

@lafriks commented on GitHub (Oct 27, 2017): @ethantkoenig Could it be that bleve was updated between 1.1 and 1.2?
GiteaMirror commented 2025-11-02 03:51:51 -06:00
Author
Owner
Copy Link

@ethantkoenig commented on GitHub (Oct 27, 2017):

No. If it was, we would have run into this problem a long time ago

@ethantkoenig commented on GitHub (Oct 27, 2017): No. If it was, we would have run into this problem a long time ago
GiteaMirror commented 2025-11-02 03:51:51 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Oct 27, 2017):

@ethantkoenig what bleve index version is used in master branch?

@lafriks commented on GitHub (Oct 27, 2017): @ethantkoenig what bleve index version is used in master branch?
GiteaMirror commented 2025-11-02 03:51:51 -06:00
Author
Owner
Copy Link

@ethantkoenig commented on GitHub (Oct 27, 2017):

7, if I recall correctly

@ethantkoenig commented on GitHub (Oct 27, 2017): 7, if I recall correctly
GiteaMirror commented 2025-11-02 03:51:51 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Oct 27, 2017):

ok, I'm closing this issue than

@lafriks commented on GitHub (Oct 27, 2017): ok, I'm closing this issue than
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 type/bug
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#1188
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?