-
Notifications
You must be signed in to change notification settings - Fork 51
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
(2.6 patch) Fix recvfrom never populating from_addr due to fromlen being zero #1108
base: releases/2.6
Are you sure you want to change the base?
Conversation
* Update all download-artifact uses to v4 * Update upload-artifact to v4 --------- Co-authored-by: Maxx Boehme <[email protected]>
Co-authored-by: Maxx Boehme <[email protected]>
CMakeLists.txt
Outdated
@@ -2,7 +2,7 @@ cmake_minimum_required(VERSION 3.12.0) | |||
|
|||
project(ni_grpc_device_server | |||
LANGUAGES C CXX | |||
VERSION 2.6.0) | |||
VERSION 2.7.0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maxxboehme i noticed that you bumped the version here. do you expect to make this fix in the main branch instead of releases/2.6.0?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yaqian256 , I had cherry picked this accidentally, I will revert it in this PR.
I initially only changed functions.py
but ran into errors on the pipeline saying some of the github actions used were outdated. I ended up cherry picking relevant changes from main but looks like I included the cmake changes incorrectly.
@maxxboehme i also created #1109 (it requires the repo admin to enable), if the bot is enabled, it can help us update github action versions. |
@jonathanou is a release patch necessary? Our process does not currently work well for patch releases of grpc-device and it causes havoc with the internal pipelines kicked off for azdo. Preferably would either have
|
What does this Pull Request accomplish?
TODO: Include high-level description of the changes in this pull request.
Why should this Pull Request be merged?
TODO: Justify why this contribution should be part of the project.
What testing has been done?
TODO: Detail what testing has been done to ensure this submission meets requirements.