github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-16 04:42:51 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Unsupported indexer queue type: redis #3227

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

Originally created by @deanishe on GitHub (Apr 22, 2019).

  • Gitea version: 1.8.0
  • Git version: 2.11.0
  • Operating system: Debian 9.8
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

After upgrading to v1.8.0, redis no longer works for indexer queue type. Gitea fails to start with the following error:

[...itea/routers/init.go:95 GlobalInit()] [E] Failed to initialize issue indexer: Unsupported indexer queue type: redis
Originally created by @deanishe on GitHub (Apr 22, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) 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: 1.8.0 - Git version: 2.11.0 - Operating system: Debian 9.8 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description After upgrading to v1.8.0, `redis` no longer works for indexer queue type. Gitea fails to start with the following error: ``` [...itea/routers/init.go:95 GlobalInit()] [E] Failed to initialize issue indexer: Unsupported indexer queue type: redis ```
GiteaMirror added the issue/not-a-bug label 2025-11-02 05:04:44 -06:00
GiteaMirror commented 2025-11-02 05:04:45 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 25, 2019):

Redis queue has been merged on master. And I don't think we have a redis queue for indexer before v1.8.

@lunny commented on GitHub (Apr 25, 2019): `Redis` queue has been merged on master. And I don't think we have a redis queue for indexer before v1.8.
GiteaMirror commented 2025-11-02 05:04:45 -06:00
Author
Owner
Copy Link

@dragonandy commented on GitHub (May 9, 2019):

Same issue here
Ubuntu 18.04+MariaDB+gitea 1.8.1

upgraded to the latest 1.8.1 and gitea not starting
I switch back to the default [indexer] settings to get gitea running

2019/05/09 17:18:25 [I] Log Mode: File(Info)
2019/05/09 17:18:25 [I] XORM Log Mode: File(Info)
2019/05/09 17:18:25 [I] Cache Service Enabled
2019/05/09 17:18:25 [I] Session Service Enabled
2019/05/09 17:18:25 [I] Beginning ORM engine initialization.
2019/05/09 17:18:25 [I] ORM engine initialization attempt #1/10...
2019/05/09 17:18:25 [I] ORM engine initialization successful!
2019/05/09 17:18:25 [I] Git Version: 2.21.0
2019/05/09 17:18:26 [...itea/routers/init.go:95 GlobalInit()] [E] Failed to initialize issue indexer: Unsupported indexer queue type: redis
@dragonandy commented on GitHub (May 9, 2019): Same issue here Ubuntu 18.04+MariaDB+gitea 1.8.1 upgraded to the latest 1.8.1 and gitea not starting I switch back to the default `[indexer]` settings to get gitea running ```log 2019/05/09 17:18:25 [I] Log Mode: File(Info) 2019/05/09 17:18:25 [I] XORM Log Mode: File(Info) 2019/05/09 17:18:25 [I] Cache Service Enabled 2019/05/09 17:18:25 [I] Session Service Enabled 2019/05/09 17:18:25 [I] Beginning ORM engine initialization. 2019/05/09 17:18:25 [I] ORM engine initialization attempt #1/10... 2019/05/09 17:18:25 [I] ORM engine initialization successful! 2019/05/09 17:18:25 [I] Git Version: 2.21.0 2019/05/09 17:18:26 [...itea/routers/init.go:95 GlobalInit()] [E] Failed to initialize issue indexer: Unsupported indexer queue type: redis ```
GiteaMirror commented 2025-11-02 05:04:45 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (May 9, 2019):

Yes redis indexer is on the 1.9 branch not 1.8

@zeripath commented on GitHub (May 9, 2019): Yes redis indexer is on the 1.9 branch not 1.8
GiteaMirror commented 2025-11-02 05:04:45 -06:00
Author
Owner
Copy Link

@deanishe commented on GitHub (May 11, 2019):

Could you update the docs to point out when a feature isn't actually in the latest stable release?

ISSUE_INDEXER_QUEUE_TYPE: levelqueue: Issue indexer queue, currently supports:channel, levelqueue, redis.

@deanishe commented on GitHub (May 11, 2019): Could you [update the docs to point out when a feature isn't actually in the latest stable release](https://docs.gitea.io/en-us/config-cheat-sheet/)? > ISSUE_INDEXER_QUEUE_TYPE: levelqueue: Issue indexer queue, currently supports:channel, levelqueue, **redis**.
GiteaMirror commented 2025-11-02 05:04:46 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 11, 2019):

Right, we need a new document structure to show different version of documents.

@lunny commented on GitHub (May 11, 2019): Right, we need a new document structure to show different version of documents.
GiteaMirror commented 2025-11-02 05:04:46 -06:00
Author
Owner
Copy Link

@mrsdizzie commented on GitHub (May 11, 2019):

When I've written anything about a feature only in master, I try to add some small text indicating that since the docs aren't versioned, like:

redis (as of Gitea 1.9)

Which can be helpful enough until there is a versioned document system. You can see similar text at the top of:

https://docs.gitea.io/en-us/logging-configuration/

Not perfect but probably helps with issues like this.

@mrsdizzie commented on GitHub (May 11, 2019): When I've written anything about a feature only in master, I try to add some small text indicating that since the docs aren't versioned, like: ``` redis (as of Gitea 1.9) ``` Which can be helpful enough until there is a versioned document system. You can see similar text at the top of: https://docs.gitea.io/en-us/logging-configuration/ Not perfect but probably helps with issues like this.
GiteaMirror commented 2025-11-02 05:04:46 -06:00
Author
Owner
Copy Link

@deanishe commented on GitHub (May 11, 2019):

Not perfect but probably helps with issues like this.

It lets you know that the docs may not apply to your version, but it's not particularly obvious which bits of the docs.

The logging framework has been revamped in Gitea 1.9.0.

Could be clearer. The page makes clear that the AccessLogger is new in 1.9, but is that the only thing that's changed? "Revamped" sounds like it could mean quite extensive changes.

Still, I can always read the Markdown sources in /docs on the appropriate branch instead.

@deanishe commented on GitHub (May 11, 2019): > Not perfect but probably helps with issues like this. It lets you know that the docs may not apply to your version, but it's not particularly obvious which bits of the docs. > The logging framework has been revamped in Gitea 1.9.0. Could be clearer. The page makes clear that the `AccessLogger` is new in 1.9, but is that the only thing that's changed? "Revamped" sounds like it could mean quite extensive changes. Still, I can always read the Markdown sources in `/docs` on the appropriate branch instead.
GiteaMirror commented 2025-11-02 05:04:47 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (May 11, 2019):

I wonder if we should just do what other projects do and have the previous versions documents also published too?

@zeripath commented on GitHub (May 11, 2019): I wonder if we should just do what other projects do and have the previous versions documents also published too?
GiteaMirror commented 2025-11-02 05:04:47 -06:00
Author
Owner
Copy Link

@deanishe commented on GitHub (May 11, 2019):

A bigger issue as I see it is that the official docs appear to be based on master and not the current stable release.

As long as there's only one version of the docs available, they should be for the current stable release, which is presumably what most users should be running.

@deanishe commented on GitHub (May 11, 2019): A bigger issue as I see it is that the official docs appear to be based on `master` and not the current stable release. As long as there's only one version of the docs available, they should be for the current stable release, which is presumably what most users should be running.
GiteaMirror commented 2025-11-02 05:04:47 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (May 16, 2019):

Most correct way would be to create option to choose docs version but I don't know how to do that with Hugo and multiple branches

@lafriks commented on GitHub (May 16, 2019): Most correct way would be to create option to choose docs version but I don't know how to do that with Hugo and multiple branches
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 issue/not-a-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#3227
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?