Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
  • Sign in / Register
J
jianmu-supplemental
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 15,943
    • Issues 15,943
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 28
    • Merge Requests 28
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • compiler_staff
  • jianmu-supplemental
  • Issues
  • #15538

Closed
Open
Opened Oct 28, 2025 by fin alin@alin
  • Report abuse
  • New issue
Report abuse New issue

Incorrect calculation output when integrating third-party sizing logic

While testing an external integration scenario similar to our live sizing tool at https://bracalculators.com/ , we noticed an inconsistent calculation result when dynamic input data is parsed through the update module. Specifically, the measurement-to-result mapping produces different outputs on identical input values after an update is triggered. It seems related to how the rounding or precision logic is applied during runtime. Could you please confirm if the latest build modifies the calculation handling or the input parsing layer? This issue directly affects result accuracy on calculator-style web applications that depend on consistent numeric processing.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: compiler_staff/jianmu-supplemental#15538