Skip to content

Conversation

@PVince81
Copy link
Member

@PVince81 PVince81 commented Dec 9, 2021

In case of error there is no guarantee that $source or $target is set or
is a resource when handling an error.

Without this fix, there's a risk that fclose will fail and the actual
exception will not be thrown, making it impossible to find out about the
root cause.

In case of error there is no guarantee that $source or $target is set or
is a resource when handling an error.

Without this fix, there's a risk that fclose will fail and the actual
exception will not be thrown, making it impossible to find out about the
root cause.

Signed-off-by: Vincent Petry <[email protected]>
@PVince81
Copy link
Member Author

PVince81 commented Dec 9, 2021

/backport to stable23

@PVince81
Copy link
Member Author

PVince81 commented Dec 9, 2021

/backport to stable22

@PVince81
Copy link
Member Author

PVince81 commented Dec 9, 2021

/backport to stable21

@Pytal Pytal added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Dec 9, 2021
@Pytal Pytal merged commit c019e33 into master Dec 9, 2021
@Pytal Pytal deleted the bugfix/noid/encryption-wrapper-fclose-check branch December 9, 2021 23:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to release Ready to be released and/or waiting for tests to finish bug feature: encryption (server-side)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants