Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • S seismic-dms-cpp-lib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • 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-cpp-lib
  • Merge requests
  • !94

fix: azure-curl provider exception type leaks to through core apis to customer!

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Anthony Lichnewsky requested to merge slb/al/azure-curl-object-size-throws-workaround into master Sep 15, 2021
  • Overview 3
  • Commits 1
  • Pipelines 9
  • Changes 3

built on top of MR !91 (merged) that allows upgrade to recent libxml2 fixes the build of experimental providers.

This is a workaround.

The correct things to consider doing are :

  • make -1LL a constant for Storage::MISSING_OBJECT_SIZE or the like
  • return that instead of an exception in all providers
  • make sure no provider dependent exception type leaks. the customer must not have to write new error handling code when changing cloud provider.
  • potentially return stack trace in exception messages...

( current code just sent "Blob does not exist" message. to a call trying to write a new blob... )

Edited Sep 21, 2021 by Anthony Lichnewsky
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: slb/al/azure-curl-object-size-throws-workaround