greatbit / quack

Web Based Test Management System
Apache License 2.0
116 stars 34 forks source link

Exception in log when test case update error is displayed on console #247

Closed bobbeck55 closed 1 year ago

bobbeck55 commented 1 year ago

2 browser test scenario browser 1 - edit test case x and edit attribute y browser 2 - edit test case x and edit attribute y browser 1 - delete 1 value from attribute y browser 2 - attempt to save attribute y with change - error on browser and exception in log. Error on console makes sense. Why exception in log? Is this a problem? Here are config files and log.

version: '2'

volumes: data: external: true

services: quack: image: greatbit/quack ports:

azee commented 1 year ago

Exception is not a bug, it is a way to manipulate the flow of the application. Exception is being converted into a valid non-200 response from the API that UI interprets and processes depending on the response code and message. It is a "WARN" long. An absolutely legit race condition, or "optimistic locking" scenario, when 2 people are updating 1 entity at the same time and we do not want lost updates from the first one.

bobbeck55 commented 1 year ago

Good work

On Tue, Feb 28, 2023 at 8:43 AM Azee @.***> wrote:

Exception is not a bug, it is a way to manipulate the flow of the application. Exception is being converted into a valid non-200 response from the API that UI interprets and processes depending on the response code and message. It is a "WARN" long. An absolutely legit race condition, or "optimistic locking" scenario, when 2 people are updating 1 entity at the same time and we do not want lost updates from the first one.

— Reply to this email directly, view it on GitHub https://github.com/greatbit/quack/issues/247#issuecomment-1448202772, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZWTTVST6FQ5KNDA6WLY43LWZX6JDANCNFSM6AAAAAAVKXMZOA . You are receiving this because you authored the thread.Message ID: @.***>