Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beat
  • beat.webbeat.web
  • Issues
  • #83
Closed
Open
Created Dec 04, 2014 by Laurent EL SHAFEY@laurent.el-shafey

Django FloatField does not handle +/-inf and NaN values

The current version of Django (1.7.1) has a FloatField implementation that does not support special floating point values such as +/-inf and NaN.

The following Django ticket mentions this issue: https://code.djangoproject.com/ticket/4287

This is currently a problem with our analyzers that store results as FloatField in the SQL database. When such a value is passed from the scheduler to the web (e.g. in the block_finished method), an error occurs (500: internal server error), which leads to the messsage to be continuously sent and misprocessed.

We need to find a workaround for this.

Assignee
Assign to
Time tracking