Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #248, change blocktype value used for custody #250

Merged
merged 1 commit into from
Sep 27, 2023

Conversation

jphickey
Copy link
Collaborator

Describe the contribution
Change the custody signal blocktype from 13 to 73

Fixes #248

Testing performed
Interoperability testing with remote node using different BP software

Expected behavior changes
Will not conflict with custom blocktype used by remote software

System(s) tested on
Debian

Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

Change the custody signal blocktype from 13 to 73
@jphickey jphickey added the ccb:ready Pull request is ready for CCB discussion label Sep 20, 2023
@jphickey jphickey added ccb:approved Pull request has been granted final approval for merging. All required process objectives are met. and removed ccb:ready Pull request is ready for CCB discussion labels Sep 27, 2023
@jphickey
Copy link
Collaborator Author

Reviewed and approved at 2023-09-27 CCB

@jphickey jphickey merged commit 111392c into nasa:main Sep 27, 2023
8 checks passed
@jphickey jphickey deleted the fix-248-blocktype branch November 14, 2023 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ccb:approved Pull request has been granted final approval for merging. All required process objectives are met.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use different block type value for custody signaling
2 participants