Skip to content
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

Update lunny/levelqueue to prevent NPE when reads are performed after close #20534

Merged
merged 1 commit into from
Jul 29, 2022
Merged

Update lunny/levelqueue to prevent NPE when reads are performed after close #20534

merged 1 commit into from
Jul 29, 2022

Commits on Jul 29, 2022

  1. Update lunny/levelqueue to prevent NPE when reads are performed after… 

    … close

go-gitea#20380 reveals that there was a slight bug in the levelqueue code that assumed that
reads and write would not occur after the db is closed. This unfortunately cannot be
assumed, and if a read or write occured this would result in a NPE.

This bug has been fixed in f020868cc2f78a4bb0b110c4c232c74be048453e therefore this
PR updates Gitea to use this.

Fix go-gitea#20380

Signed-off-by: Andrew Thornton <art27@cantab.net>
    @zeripath
    zeripath committed Jul 29, 2022
    Configuration menu
    Copy the full SHA
    10ffb30 View commit details
    Browse the repository at this point in the history