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.

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

[FIX] barcode: set the max_time_between_keys_in_ms to 100 by default #101128

Conversation

phwa-odoo
Copy link

The default value of max_time_between_keys_in_ms in barcode is 55 ms. The default value of 55 ms is too low and creates an issue for RFID readers.

The default value of max_time_between_keys_in_ms is increased to 100 ms.

task-2996072

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

The default value of max_time_between_keys_in_ms in barcode is 55 ms.
The default value of 55 ms is too low and creates an issue for RFID readers.

The default value of max_time_between_keys_in_ms is increased to 100 ms.

task-2996072
@robodoo
Copy link
Contributor

robodoo commented Sep 26, 2022

Pull request status dashboard

@C3POdoo C3POdoo requested review from a team September 26, 2022 12:45
@rdeodoo rdeodoo removed the request for review from a team September 26, 2022 12:48
@C3POdoo C3POdoo added the RD research & development, internal work label Sep 26, 2022
@kbapt
Copy link
Contributor

kbapt commented Sep 27, 2022

@odoo/rd-security could you review this PR please?
The timeout has been created to 100ms to make RFID readers work more reliably as 55ms was too short sometimes.

Thanks

Copy link
Contributor

@mart-e mart-e left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kba-odoo security wise, no problem :)

@kbapt
Copy link
Contributor

kbapt commented Sep 27, 2022

robodoo r+

robodoo pushed a commit that referenced this pull request Sep 27, 2022
The default value of max_time_between_keys_in_ms in barcode is 55 ms.
The default value of 55 ms is too low and creates an issue for RFID readers.

The default value of max_time_between_keys_in_ms is increased to 100 ms.

task-2996072

closes #101128

Signed-off-by: Kevin Baptiste <kba@odoo.com>
@kbapt
Copy link
Contributor

kbapt commented Sep 27, 2022

@kba-odoo security wise, no problem :)

damn 🤦‍♂️ I thought the ci/security was red... my bad :-D

@robodoo robodoo temporarily deployed to merge September 27, 2022 08:11 Inactive
@robodoo robodoo closed this Sep 27, 2022
@fw-bot fw-bot deleted the 13.0-barcode-increase-max-time-between-keys-phwa branch October 11, 2022 08:47
gamarino pushed a commit to numaes/numa-public-odoo that referenced this pull request Jan 11, 2023
The default value of max_time_between_keys_in_ms in barcode is 55 ms.
The default value of 55 ms is too low and creates an issue for RFID readers.

The default value of max_time_between_keys_in_ms is increased to 100 ms.

task-2996072

closes odoo/odoo#101128

Signed-off-by: Kevin Baptiste <kba@odoo.com>
zamberjo pushed a commit to aurestic/OpenUpgrade that referenced this pull request Mar 1, 2023
The default value of max_time_between_keys_in_ms in barcode is 55 ms.
The default value of 55 ms is too low and creates an issue for RFID readers.

The default value of max_time_between_keys_in_ms is increased to 100 ms.

task-2996072

closes odoo/odoo#101128

Signed-off-by: Kevin Baptiste <kba@odoo.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RD research & development, internal work
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants