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
  • F FIORest
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • FNAR Industries
  • FIO
  • FIORest
  • Merge requests
  • !27

Rework how BadRequests are stored. At the root is directories grouped by the...

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Tom Sakks requested to merge feature/ReworkBadRequests into develop Sep 03, 2021
  • Overview 0
  • Commits 2
  • Pipelines 2
  • Changes 1

Rework how BadRequests are stored. At the root is directories grouped by the exception message's hashcode. After that, it's by 'DateTime.UtcNow.Ticks-USERNAME'. Followed by the previous files.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: feature/ReworkBadRequests