Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.web
beat.web
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • beat
  • beat.webbeat.web
  • Issues
  • #557

Closed
Open
Opened Aug 03, 2020 by Samuel GAIST@samuel.gaist
  • Report abuse
  • New issue
Report abuse New issue

Experiment put may fail due to spur PUT calls

This issue appears currently only with Safari.

When accessing an experiment it sometimes sends a PUT command that does not follow through but still runs through enough of the machinery to trigger an error.

The error comes from the fact that the writing serializer class is set to None as the put handling is currently custom implemented unlike the other subclasses of RetrieveUpdateDestroyContributionView.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
2
Labels
bug confirmed
Assign labels
  • View project labels
Reference: beat/beat.web#557