Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • GlitchTip Backend GlitchTip Backend
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GlitchTipGlitchTip
  • GlitchTip BackendGlitchTip Backend
  • Issues
  • #112
Closed
Open
Created Nov 10, 2021 by james kiger@james.kigerOwner

Uptime accepts large intervals that produce an error

You can currently successfully submit a large interval for an uptime monitor resulting in repeated errors on the backend:
worker_1 | Traceback (most recent call last): worker_1 | File "/usr/local/lib/python3.9/site-packages/celery/app/trace.py", line 450, in trace_task worker_1 | R = retval = fun(*args, **kwargs) worker_1 | File "/usr/local/lib/python3.9/site-packages/celery/app/trace.py", line 731, in __protected_call__ worker_1 | return self.run(*args, **kwargs) worker_1 | File "/code/glitchtip/uptime/tasks.py", line 43, in dispatch_checks worker_1 | for i, monitor_id in enumerate(monitor_ids.iterator(), 1): worker_1 | File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 353, in _iterator worker_1 | yield from self._iterable_class(self, chunked_fetch=use_chunked_fetch, chunk_size=chunk_size) worker_1 | File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 171, in __iter__ worker_1 | for row in compiler.results_iter(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size): worker_1 | File "/usr/local/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1646, in cursor_iter worker_1 | for rows in iter((lambda: cursor.fetchmany(itersize)), sentinel): worker_1 | File "/usr/local/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1646, in <lambda> worker_1 | for rows in iter((lambda: cursor.fetchmany(itersize)), sentinel): worker_1 | File "/usr/local/lib/python3.9/site-packages/django/db/utils.py", line 97, in inner worker_1 | return func(*args, **kwargs) worker_1 | File "/usr/local/lib/python3.9/site-packages/django/db/utils.py", line 90, in __exit__ worker_1 | raise dj_exc_value.with_traceback(traceback) from exc_value worker_1 | File "/usr/local/lib/python3.9/site-packages/django/db/utils.py", line 97, in inner worker_1 | return func(*args, **kwargs) worker_1 | django.db.utils.DataError: timestamp out of range
The interval I used was "115740740 17:46:39"

Edited Nov 10, 2021 by james kiger
Assignee
Assign to
Time tracking