gitea/helm-gitea
Fork 169
Code Issues 54 Pull Requests 11 Actions Releases 103 Activity

Pull Request failed in latest Chart Version #173

New Issue
Closed
opened 2021-06-09 14:28:41 +00:00 by Jonas18175 · 4 comments
Jonas18175 commented 2021-06-09 14:28:41 +00:00
Copy Link

Hello,

in the latest chart version the pull requests failed.
The log shows:

2021/06/09 14:13:02 ...rvices/pull/patch.go:105:checkConflicts() [E] Unable to create temporary patch file! Error: open /tmp/gitea/patch352582093: permission denied 9.6.2021 16:13:02 2021/06/09 14:13:02 .../api/v1/repo/pull.go:431:CreatePullRequest() [E] NewPullRequest: Unable to create temporary patch file! Error: open /tmp/gitea/patch352582093: permission denied

I check the tmp folder and there are a gitea folder with full rights for the gitea user. I temporary change that to 777 permissions in runtime and the pull requests works again. Seems that it use a other user to access it and not git, but why? I thougth that gitea runs as user git inside container.

Hello, in the latest chart version the pull requests failed. The log shows: ``` 2021/06/09 14:13:02 ...rvices/pull/patch.go:105:checkConflicts() [E] Unable to create temporary patch file! Error: open /tmp/gitea/patch352582093: permission denied 9.6.2021 16:13:02 2021/06/09 14:13:02 .../api/v1/repo/pull.go:431:CreatePullRequest() [E] NewPullRequest: Unable to create temporary patch file! Error: open /tmp/gitea/patch352582093: permission denied ``` I check the tmp folder and there are a gitea folder with full rights for the gitea user. I temporary change that to 777 permissions in runtime and the pull requests works again. Seems that it use a other user to access it and not git, but why? I thougth that gitea runs as user git inside container.
Jonas18175 commented 2021-06-09 14:35:08 +00:00
Author
Copy Link

Is possible fixed with: f0070ef64b

Is possible fixed with: https://gitea.com/gitea/helm-chart/commit/f0070ef64bcb8fa91ac16acdd11f923235a552fa
luhahn commented 2021-06-09 14:35:41 +00:00
Member
Copy Link

should be fixed with #172

should be fixed with #172
luhahn commented 2021-06-09 14:37:06 +00:00
Member
Copy Link

Released 3.1.3 with the fix, can you confirm, that this is fixed for you?

Released 3.1.3 with the fix, can you confirm, that this is fixed for you?
Jonas18175 commented 2021-06-09 18:57:41 +00:00
Author
Copy Link

Yes, its fixed for me. I confirmed. Thanks ?

Yes, its fixed for me. I confirmed. Thanks ?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
workaround
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
42wim 6543 a1012112796 Akkuman appleboy axifive betacat0 blumia bwko caicandong ChristopherHX DaanSelen davidsvantesson delvh denyskon fuxiaohei gary-kim garymoon giteabot guillep2k HesterG hiifong jaqra jolheiser jonasfranz jpraet kdumontnu kemzeb kerwin612 khmarbaise KN4CK3R kolaente lafriks lng2020 lotherk luhahn lunny mrsdizzie noerw pat-s puni9869 renovate-bot richmahn rossigee sapk screenshots sillyguodong silverwind smartclip_tim strk tboerger techknowlogick TheFox0x7 tobiasbp typeless volker.raschek wolfogre wxiaoguang yardenshoham yp05327 zeripath Zettat123
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gitea/helm-gitea#173
No description provided.
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?