Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • S seismic-dms-service
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 49
    • Issues 49
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and 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
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Domain Data Management Services
  • Seismic
  • Seismic DMS Suite
  • seismic-dms-service
  • Merge requests
  • !92

added reason for 423 error message

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Diego Molteni requested to merge trusted-slb/dm3/reason-423 into master May 18, 2021
  • Overview 0
  • Commits 0
  • Pipelines 2
  • Changes 0

Added Reason Code to the 423 Error Message. Clients applications can better detect the status of the lock error and correctly handle their flow. The Reason is a string code placed at the end to the error message an has this form:

"[" + RCODE(fixed-tag) + ":" + REASON-CODE(2-char-code) + TTL(sec-number) + "]"

The REASON-CODE possible values are:

  • WL: The dataset is write locked
  • RL: The dataset is read locked
  • CL: The dataset can't be locked (lock cache mutex can't be acquired)
  • CU: The dataset can't be unlocked (lock cache mutex can't be released)

For example:

[seismic-store] The dataset is write locked [RCODE:WL3600]

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: trusted-slb/dm3/reason-423