Skip to content
GitLab
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
  • beatbeat
  • beat.webbeat.web
  • Issues
  • #557
Closed
Open
Issue created Aug 03, 2020 by Samuel GAIST@samuel.gaistOwner

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
Time tracking