OSDU Software issueshttps://community.opengroup.org/groups/osdu/-/issues2021-07-06T15:38:33Zhttps://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/issues/23Spotbugs Failing in some Services with Out of Memory Exception2021-07-06T15:38:33ZDavid Diederichd.diederich@opengroup.orgSpotbugs Failing in some Services with Out of Memory ExceptionSome services, such as [Partition](https://community.opengroup.org/osdu/platform/system/partition/-/jobs/404507) fail in the spotbugs step. If re-run with `SECURE_LOG_LEVEL` set to `"debug"`, we see that the [failure](https://community.o...Some services, such as [Partition](https://community.opengroup.org/osdu/platform/system/partition/-/jobs/404507) fail in the spotbugs step. If re-run with `SECURE_LOG_LEVEL` set to `"debug"`, we see that the [failure](https://community.opengroup.org/osdu/platform/system/partition/-/jobs/404635#L878) is `java.lang.OutOfMemoryError`
From that [same debug output](https://community.opengroup.org/osdu/platform/system/partition/-/jobs/404635#L868), spotbugs is run with `java -Xmx1900M`.M7 - Release 0.10David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/storage/-/issues/73Storage ACL validation (for Azure implementation) is performed against Entitl...2021-07-27T21:16:00ZAlok JoshiStorage ACL validation (for Azure implementation) is performed against Entitlements V1 databaseAzure's [CloudStorageImpl](https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/provider/storage-azure/src/main/java/org/opengroup/osdu/storage/provider/azure/CloudStorageImpl.java) class's write method calls `valid...Azure's [CloudStorageImpl](https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/provider/storage-azure/src/main/java/org/opengroup/osdu/storage/provider/azure/CloudStorageImpl.java) class's write method calls `validateRecordAcls` to perform ACL validation.
The existence of ACL is checked against the Entitlements V1 database, which is the issue. The ACL validation should be performed against Entitlements service, so that the responsibility falls on Entitlements service. If such api is not available, the ACL validation should be done against the new Entitlements V2 databaseM7 - Release 0.10Neelesh ThakurNeelesh Thakurhttps://community.opengroup.org/osdu/platform/home/-/issues/37Version endpoint - Part 1 (Storage Service)2021-08-13T12:21:04ZKateryna Kurach (EPAM)Version endpoint - Part 1 (Storage Service)Issue that tracks M8 activities: https://community.opengroup.org/osdu/platform/home/-/issues/36
I'd like to propose a new endpoint for all services to retrieve the version information. I'm most interested in the tag version / upcoming t...Issue that tracks M8 activities: https://community.opengroup.org/osdu/platform/home/-/issues/36
I'd like to propose a new endpoint for all services to retrieve the version information. I'm most interested in the tag version / upcoming tag version. My thinking is maven-centric, but I'd like to get the artifact version injected into the jar files and available via a simple GET endpoint.
I have several use cases in mind right now:
1. The end customer should have a way to query their environment to know what versions they are running. Then they would know that patches they see coming in on community have been applied to their environment. The Admin UI may be able to use this endpoint to make that query easier.
1. Application developers would be able to query versions of the services they are working with to determine compatibility.
1. The CI pipeline can query the running instances of dependent services, and issue a warning if the major/minor doesn't match the currently executing one. Have branch names or commit hashes would further improve this, but isn't part of my initial thinking.
What complexities and challenges do you see in trying to provide this information?M7 - Release 0.10https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/issues/16Wellbore DMS - APIs for WellLog, WellTrajectory and WellboreMarkerSet2021-07-21T10:31:07ZGisele SouzaWellbore DMS - APIs for WellLog, WellTrajectory and WellboreMarkerSet- New APIs for bulk and meta data of the following WPC: WellLog, WellTrajectory and WellboreMarkerSet
- Unit tests/integration tests to validate the new APIs- New APIs for bulk and meta data of the following WPC: WellLog, WellTrajectory and WellboreMarkerSet
- Unit tests/integration tests to validate the new APIsM7 - Release 0.10Gisele SouzaGisele Souza2021-07-21https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/issues/38WITSML Ingestion (WITSML parsers and WITSML ingestion )2021-07-28T13:41:47Zjingdong sunWITSML Ingestion (WITSML parsers and WITSML ingestion )M7 - Release 0.10Anuj GuptaShaonGregjingdong sunAnuj Guptahttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/95Workflow API authorization failure should throw 401/403 not 4042021-07-21T14:40:45ZMatt WiseWorkflow API authorization failure should throw 401/403 not 404When a user is not valid or a valid user does not have the entitlements group required to call /api/workflow/v1/workflow, they are returned a 404 error. This should follow entitlements convention and return a 401/403 depending on the ca...When a user is not valid or a valid user does not have the entitlements group required to call /api/workflow/v1/workflow, they are returned a 404 error. This should follow entitlements convention and return a 401/403 depending on the case.
![image](/uploads/d414580f319bcadb0fe7575fb8763ca4/image.png)M7 - Release 0.10Dania Kodeih (Microsoft)Wladmir FrazaoJoeDmitriy RudkoMatt WiseAlan HensonDania Kodeih (Microsoft)https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/92Workflow property validation should be done at the API level2021-07-27T14:46:45ZMatt WiseWorkflow property validation should be done at the API levelCurrently, it seems it is left up to each provider implementation to properly validate fields like 'WorkflowName'.
This should be an API validation instead in the core code.
Example: WorkflowName regex check in provider code
![image](...Currently, it seems it is left up to each provider implementation to properly validate fields like 'WorkflowName'.
This should be an API validation instead in the core code.
Example: WorkflowName regex check in provider code
![image](/uploads/af09db72f6882c102853ab8751a70873/image.png)M7 - Release 0.10ethiraj krishnamanaiduDania Kodeih (Microsoft)Wladmir FrazaoJoeChris ZhangDmitriy RudkoSpencer Suttonsuttonsp@amazon.comMatt Wiseethiraj krishnamanaidu