- Reset the incorrect PIN attempts to 0 when the PIN is reset
- Reset the flag_account_blocked if the PIN attempts is 0
- Resolves issue https://git.grassecon.net/urdt/ussd/issues/280
why is the check for incorrect pin attempts needed here? Why not just put it as part of the incorrect pin reset? Wouldn't that reduce the need for one read operation?
why is the check for incorrect pin attempts needed here? Why not just put it as part of the incorrect pin reset? Wouldn't that reduce the need for one read operation?
The check exists to reset the flag once the user access the menu.
Having the operation as part of the PIN reset increased complexity as we need to access the state of the user, reset the account blocked flag and save the state
The check exists to reset the flag once the user access the menu.
Having the operation as part of the PIN reset increased complexity as we need to access the state of the user, reset the account blocked flag and save the state
Hmm. Ok. It's not entirely clear to me why it is like this, as any point where the pin is reset would simply enable to set the flag as reset? There would be no need to read the flag?
Hmm. Ok. It's not entirely clear to me why it is like this, as any point where the pin is reset would simply enable to set the flag as reset? There would be no need to read the flag?
lash
merged commit 7d513ac2a7 into master2025-01-21 07:47:33 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
@@ -256,0 +265,4 @@return res, fmt.Errorf("missing session")}currentWrongPinAttempts, err := store.ReadEntry(ctx, sessionId, storedb.DATA_INCORRECT_PIN_ATTEMPTS)why is the check for incorrect pin attempts needed here? Why not just put it as part of the incorrect pin reset? Wouldn't that reduce the need for one read operation?
The check exists to reset the flag once the user access the menu.
Having the operation as part of the PIN reset increased complexity as we need to access the state of the user, reset the account blocked flag and save the state
Hmm. Ok. It's not entirely clear to me why it is like this, as any point where the pin is reset would simply enable to set the flag as reset? There would be no need to read the flag?