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

Gitea act not able to run #10607

New Issue
Closed
opened 2025-11-02 09:12:29 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 09:12:29 -06:00
Owner
Copy Link

Originally created by @rodude123 on GitHub (Apr 7, 2023).

Description

When I try to run the act daemon, I get this error what do I do? There's not enough documentation on how to set this up yet, I think since it's way too new.

INFO[0000] Starting runner daemon                       
INFO[2023-04-07T10:23:06+01:00] gc: 2023-04-07 10:23:06.050623535 +0100 BST m=+0.018931049  module=cache_request
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xea021b]

goroutine 10 [running]:
gitea.com/gitea/act_runner/internal/app/poll.(*Poller).fetchTask(0xc000518ac0, {0x1238c98?, 0xc00045abc0?})
        gitea.com/gitea/act_runner/internal/app/poll/poller.go:78 +0x1db
gitea.com/gitea/act_runner/internal/app/poll.(*Poller).poll(0xc000518ac0, {0x1238c98, 0xc00045abc0}, 0x0?, 0x0?)
        gitea.com/gitea/act_runner/internal/app/poll/poller.go:55 +0xc6
created by gitea.com/gitea/act_runner/internal/app/poll.(*Poller).Poll
        gitea.com/gitea/act_runner/internal/app/poll/poller.go:41 +0x6c

Gitea Version

Gitea version 1.19.0 built with GNU Make 4.1, go1.20.2 : bindata, sqlite, sqlite_unlock_notify, pam, cert

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.34.1

Operating System

Ubuntu 22.04

How are you running Gitea?

I'm running the base Linux binary through a systemd service under a specific user. I'm running Ubuntu 22.04

Database

SQLite

Originally created by @rodude123 on GitHub (Apr 7, 2023). ### Description When I try to run the act daemon, I get this error what do I do? There's not enough documentation on how to set this up yet, I think since it's way too new. ``` INFO[0000] Starting runner daemon INFO[2023-04-07T10:23:06+01:00] gc: 2023-04-07 10:23:06.050623535 +0100 BST m=+0.018931049 module=cache_request panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xea021b] goroutine 10 [running]: gitea.com/gitea/act_runner/internal/app/poll.(*Poller).fetchTask(0xc000518ac0, {0x1238c98?, 0xc00045abc0?}) gitea.com/gitea/act_runner/internal/app/poll/poller.go:78 +0x1db gitea.com/gitea/act_runner/internal/app/poll.(*Poller).poll(0xc000518ac0, {0x1238c98, 0xc00045abc0}, 0x0?, 0x0?) gitea.com/gitea/act_runner/internal/app/poll/poller.go:55 +0xc6 created by gitea.com/gitea/act_runner/internal/app/poll.(*Poller).Poll gitea.com/gitea/act_runner/internal/app/poll/poller.go:41 +0x6c ``` ### Gitea Version Gitea version 1.19.0 built with GNU Make 4.1, go1.20.2 : bindata, sqlite, sqlite_unlock_notify, pam, cert ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.34.1 ### Operating System Ubuntu 22.04 ### How are you running Gitea? I'm running the base Linux binary through a systemd service under a specific user. I'm running Ubuntu 22.04 ### Database SQLite
GiteaMirror added the type/bug label 2025-11-02 09:12:29 -06:00
GiteaMirror commented 2025-11-02 09:12:30 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 7, 2023):

Please upgrade to the latest version and please fire similiar issues in https://gitea.com/gitea/act_runner .

@lunny commented on GitHub (Apr 7, 2023): Please upgrade to the latest version and please fire similiar issues in https://gitea.com/gitea/act_runner .
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#10607
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?