Skip to content

Error on dexer/stats/queue.go #18847

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
lds-lds opened this issue Feb 21, 2022 · 6 comments · Fixed by #18870
Closed

Error on dexer/stats/queue.go #18847

lds-lds opened this issue Feb 21, 2022 · 6 comments · Fixed by #18870

Comments

@lds-lds
Copy link

lds-lds commented Feb 21, 2022

Gitea Version

1.15.11

Git Version

2.7.4

Operating System

ubuntu/xenial

How are you running Gitea?

i run gitea by systemd /etc/systemd/system/gitea.service

[Unit]
Description=Gitea (Git with a cup of tea)
After=syslog.target
After=network.target
After=mysqld.service

[Service]

LimitMEMLOCK=infinity
LimitNOFILE=65535
RestartSec=2s
Type=simple
User=git
Group=git
WorkingDirectory=/home/git/gitea
ExecStart=/home/git/gitea/gitea web
Restart=always
Environment=USER=git HOME=/home/git

[Install]
WantedBy=multi-user.target

Database

MySQL

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

Hello
I see this error in the gitea log
What can I do to correct it?

2022/02/21 15:05:06 ...dexer/stats/queue.go:24:handle() [E] stats queue indexer.Index(409) failed: no such file or directory

Screenshots

No response

@zeripath
Copy link
Contributor

I suspect the repository with ID 409 does not exist on the filesystem

@zeripath
Copy link
Contributor

Yes - this is the problem:

The repository directory for repository ID 409 does not exist.

zeripath added a commit to zeripath/gitea that referenced this issue Feb 23, 2022
Repositories missing their directory should not report an error from the stats
indexer.

Close go-gitea#18847

Signed-off-by: Andrew Thornton <[email protected]>
techknowlogick pushed a commit that referenced this issue Feb 25, 2022
Repositories missing their directory should not report an error from the stats
indexer.

Close #18847

Signed-off-by: Andrew Thornton <[email protected]>

Co-authored-by: Lunny Xiao <[email protected]>
@lds-lds
Copy link
Author

lds-lds commented Feb 25, 2022

Thanks @techknowlogick for your explanation

@lds-lds
Copy link
Author

lds-lds commented Feb 28, 2022

hello @techknowlogick
the repository 409 exist on file system and on database ...

MariaDB [gitea]> select * from repository where id = '409';
+-----+----------+------------+------------+----------+-------------+---------+-----------------------+--------------+----------------+-------------+-----------+-----------+------------+-------------------+-----------+------------------+----------------+-----------------------+--------------+---------------------+------------+----------+-------------+-----------+--------+---------+---------+-------------+-------------+--------+-----------------+---------------------------------------+--------+-------------+--------+--------------+--------------+
| id  | owner_id | owner_name | lower_name | name     | description | website | original_service_type | original_url | default_branch | num_watches | num_stars | num_forks | num_issues | num_closed_issues | num_pulls | num_closed_pulls | num_milestones | num_closed_milestones | num_projects | num_closed_projects | is_private | is_empty | is_archived | is_mirror | status | is_fork | fork_id | is_template | template_id | size   | is_fsck_enabled | close_issues_via_commit_in_any_branch | topics | trust_model | avatar | created_unix | updated_unix |
+-----+----------+------------+------------+----------+-------------+---------+-----------------------+--------------+----------------+-------------+-----------+-----------+------------+-------------------+-----------+------------------+----------------+-----------------------+--------------+---------------------+------------+----------+-------------+-----------+--------+---------+---------+-------------+-------------+--------+-----------------+---------------------------------------+--------+-------------+--------+--------------+--------------+
| 409 |       23 | xxxxxxx   | koha-env   | koha-env |             |         |                     0 | NULL         | master         |           1 |         0 |         0 |          0 |                 0 |         0 |                0 |              0 |                     0 |            0 |                   0 |          1 |        0 |           0 |         0 |      0 |       0 |       0 |           0 |        NULL | 286720 |               0 |                                     0 | []     |        NULL | NULL   |   1535354260 |   1535354262 |
+-----+----------+------------+------------+----------+-------------+---------+-----------------------+--------------+----------------+-------------+-----------+-----------+------------+-------------------+-----------+------------------+----------------+-----------------------+--------------+---------------------+------------+----------+-------------+-----------+--------+---------+---------+-------------+-------------+--------+-----------------+---------------------------------------+--------+-------------+--------+--------------+--------------+
ls ~/xxxxxxx/koha-env.git/
hooks

@zeripath
Copy link
Contributor

That is not a valid git repository.

A git repository is more than just a hooks directory.

@lds-lds
Copy link
Author

lds-lds commented Mar 1, 2022

how can I do to correctly delete this repository? because I do not see it in the interface of gitea
just rm repositoy and delete the row ? like:

rm -r ~/xxxxxxx/koha-env.git/ *
mysql -e "delete from repository WHERE where id = '409';"
``
It would be too simple :)

Chianina pushed a commit to Chianina/gitea that referenced this issue Mar 28, 2022
…8870)

Repositories missing their directory should not report an error from the stats
indexer.

Close go-gitea#18847

Signed-off-by: Andrew Thornton <[email protected]>

Co-authored-by: Lunny Xiao <[email protected]>
@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants