Develop Update Submodules

[Michael7371]

PR Details

Description

Updating submodules using this command: git submodule update --remote --merge

• asn1_codec: Updating the commit reference from b73989 to commit 792abc0.
• jpo-cvdp: Updating the commit reference from fa9c0ab to the commit 4d1ba2e.
• jpo-s3-deposit: Updating the commit reference from 2880f82 to commit 4566ed1.
• jpo-sdw-depositor: Updating the commit reference from be99dcc to commit 00c070f.
• jpo-security-svcs: Updating the commit reference from 2c30cd2 to commit 7e6a733.

Related Issue

N/A

Motivation and Context

Includes many changes, one of which is that this commit includes the J2735 ASN file. Also noticed that many other modules were out of date.

How Has This Been Tested?

The submodules updated have already been thoroughly tested, this just updates the reference to those modules.

Types of changes

• Defect fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that cause existing functionality to change)
• Update submodule references

Checklist:

• I have added any new packages to the sonar-scanner.properties file
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
  ODE Contributing Guide
• I have added tests to cover my changes.
• All new and existing tests passed.

[paulbourelly999]

@TonyEnglish @Michael7371 Discovered issue with this fork. Was able to build docker images successfully by using git clone --recurse-submodules but ran into issue running kafka container from docker compose. Issue is related to https://github.com/Michael7371/jpo-ode/blob/47d21847a2f087545d7e9ff367e70b07478c881a/docker-compose.yml#L37
https://github.com/Michael7371/jpo-ode/blob/47d21847a2f087545d7e9ff367e70b07478c881a/sample.env#L33.

Kafka container fails to start with the following docker compose error :

Error response from daemon: invalid volume specification: 'C:/var/run/docker.sock:/var/run/docker.sock:rw'
After removing ${DOCKER_SHARED_VOLUME_WINDOWS} from volume declaration in docker compose the issue goes away. There is no README instruction to edit this environment variable at all in installation process so maybe the README of the sample.env needs to be updated. What do you guys think? If this is not concerning I can approve the PR.

NOTE: Only tested docker build and docker compose up. Please let me know if you want me to test specific functionality

[Michael7371]

@TonyEnglish @Michael7371 Discovered issue with this fork. Was able to build docker images successfully by using git clone --recurse-submodules but ran into issue running kafka container from docker compose. Issue is related to https://github.com/Michael7371/jpo-ode/blob/47d21847a2f087545d7e9ff367e70b07478c881a/docker-compose.yml#L37 https://github.com/Michael7371/jpo-ode/blob/47d21847a2f087545d7e9ff367e70b07478c881a/sample.env#L33.

Kafka container fails to start with the following docker compose error :

Error response from daemon: invalid volume specification: 'C:/var/run/docker.sock:/var/run/docker.sock:rw' After removing ${DOCKER_SHARED_VOLUME_WINDOWS} from volume declaration in docker compose the issue goes away. There is no README instruction to edit this environment variable at all in installation process so maybe the README of the sample.env needs to be updated. What do you guys think? If this is not concerning I can approve the PR.

NOTE: Only tested docker build and docker compose up. Please let me know if you want me to test specific functionality

Hello @paulbourelly999, nice find! I was struggling to reproduce this error until I tried to use “docker compose up -d” from my WSL Ubuntu shell directly and that seemed to produce the error. Windows PowerShell didn't seem to have an issue creating the volume with the “DOCKER_SHARED_VOLUME_WINDOWS” variable set to either the “C:” value or an empty value. Let me know if this checks out with what you are seeing.

I think for now I will change the default value for that variable in the sample.env to be empty and add some documentation to the README about this error if the behavior above is the same for you.

[Michael7371]

@paulbourelly999 I pushed those changes an also created an issue to address this fully in a seperate PR: #517

[paulbourelly999]

changes an also created an issue to address this fully in a seperate PR: #517

That sounds perfect. For some reason the changes are not showing up here but are in the other PR. Is this an issue.?

[Michael7371]

changes an also created an issue to address this fully in a seperate PR: #517

That sounds perfect. For some reason the changes are not showing up here but are in the other PR. Is this an issue.?

Yes, good check! I just pushed a commit to this branch with those changes.

[paulbourelly999]

Looks good