You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
qwazix
changed the title
When Alice (a fediverse actor) tries to follow a writefreely actor (Bob) and Alice already follows Bob then writefreely crashes.
---
Aug 8, 2019
qwazix
changed the title
---
When Alice (a fediverse actor) tries to follow a writefreely actor (Bob) and Alice already follows Bob then writefreely crashes.
Aug 8, 2019
So far I think I figured out the panic, there is an error check when inserting the new actor into the remote users table which previously only checked if the error was NOT for a duplicate key. So if there was a duplicate key it would just continue on trying to proceed, however the response from the db transaction is nil when there is an error, hence the panic.
I changed the check to check for any error and can now POST duplicate follow requests, only seeing an error logged that the key was not unique.
Describe the bug
When a follow is already registered in the writefreely database, repeating the follow request crashes writefreely
Steps to reproduce (if necessary)
Steps to reproduce the behavior:
Expected behavior
Nothing probably. Or maybe refresh the public key with the new one?
Application configuration
Version or last commit: 0.10.0
log of installation, execution and crash with --debug
The text was updated successfully, but these errors were encountered: