Fixed a bug where TreeEntries were getting cached, (thanks @filipnavara) #139
No reviewers
Labels
No Label
in progress
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/security
kind/testing
kind/translation
kind/ui
lgtm/done
lgtm/need 1
lgtm/need 2
priority/critical
priority/low
priority/maybe
priority/medium
refactor
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/blocked
status/needs-feedback
status/wip
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/git#139
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Kasi-R/master"
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?
Author: @Kasi-R
Fixes the bug described at https://github.com/go-gitea/git/pull/123#issuecomment-452340523
Author: @codecov-io
Codecov Report
53.06% <0%> (ø)
Continue to review full report at Codecov.
Author: @filipnavara
On second thought, the
entriesRecursiveParsed
andentriesParsed
variables are actually never set. Either that should be fixed too, or the cache can be removed entirely (since it was never working anyway).Sorry, should have noticed that earlier, but I was blindly following the code when updating my forked code base.
Author: @Kasi-R
I guess i can add the caching check to both functions.
Edit: Updated the caching flag. Squashed the two commits.
Author: @lunny
Please send a upgrade PR to go-gitea/gitea