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.

Sign up for GitHub

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

Jump to bottom

ISO control numbers interpreted wrongfully #546

Open
robvanderveer opened this issue Aug 8, 2024 · 1 comment
Open

ISO control numbers interpreted wrongfully #546

robvanderveer opened this issue Aug 8, 2024 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers GSOC this feature is a potential Google Summer of Code candidate

Comments

@robvanderveer
Copy link
Collaborator

Spyros we have a recurring problem with the ISO numbers. there are two 7.1's and two 8.1's etc. I was pointed to it by a user. Last time this happened because 7.10 was interpreted as a value and was turned into 7.1. It should be treated as a string. I recall you fixing this.
Good to see that folks are noticing.
@northdpole northdpole removed their assignment Feb 22, 2025
@northdpole northdpole added enhancement New feature or request good first issue Good for newcomers GSOC this feature is a potential Google Summer of Code candidate labels Feb 22, 2025
@Pa04rth
Copy link
Contributor

Pa04rth commented Mar 15, 2025

I would like to solve this ,Please assign me this issue @northdpole

Pa04rth added a commit to Pa04rth/OpenCRE that referenced this issue Mar 19, 2025
@Pa04rth
Changes in db.py for solving issue OWASP#546
6903f57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request good first issue Good for newcomers GSOC this feature is a potential Google Summer of Code candidate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@robvanderveer @northdpole @Pa04rth