Skip to content

fix potential sqlite lock #1680

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.

Sign up for GitHub

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

Jump to bottom
Merged
bkcsoft merged 1 commit into from
May 8, 2017
Merged

fix potential sqlite lock #1680

bkcsoft merged 1 commit into from
May 8, 2017

Conversation

@lunny
Copy link
Member

@lunny lunny commented May 5, 2017

related #1679

@lunny lunny added the type/bug label May 5, 2017
@lunny lunny added this to the 1.2.0 milestone May 5, 2017
@lafriks
Copy link
Member

lafriks commented May 5, 2017

LGTM

@tboerger tboerger added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label May 5, 2017
@bkcsoft
Copy link
Member

bkcsoft commented May 8, 2017

LGTM

@tboerger tboerger added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels May 8, 2017
@bkcsoft bkcsoft merged commit a85c5ab into go-gitea:master May 8, 2017
@lunny lunny deleted the lunny/fix_potential_sqlite_lock branch May 8, 2017 08:21
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/bug

Projects

None yet

Milestone

1.2.0

Development

Successfully merging this pull request may close these issues.

4 participants

@lunny @lafriks @bkcsoft @tboerger