-
Notifications
You must be signed in to change notification settings - Fork 4
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
Release/2.8.0 #17
base: main
Are you sure you want to change the base?
Release/2.8.0 #17
Conversation
retrieve the server host and port from environment to have a proper comaprison
we have added now the support on the client to allow multiple servers connections
we use signal_status to send some information to the client about on-going requests
Is the build / install successful on system based on OpenSSL/1.1 and OpenSSL/3, e.g. RHEL9 ? |
…ions' into release/2.8.0 # Conflicts: # source/clientserver/xdrlib.cpp
Would anyone have an issue with reverting the API calls that were broken earlier in 2.7.0 when the new "client_flags" argument was introduced? I wanted to add a header of wrapper functions for other (accidental) breaking changes to the API (such as idamFree -> udaFree) but obviously function overloads with the same name will not work in the C layer, which applies to all the client_flags functions. In my opinion the additional argument is redundant as the call to This change will definitely take place in the uda/3.0.0 release, but I'd also like to include it in the 2.7.6 release and update 2.8.0 to follow this change. For reference, most instances occur within the source/client/accAPI.h file e.g.
The proposed new function signature would be e.g.
|
@stephen-dixon I think it is fine if this change is being added to |
Can someone add https://github.com/deepakmaroo to this PR? |
Do they need to be added as a collaborator to the uda project? I don't have the privileges to do this |
@olivhoenen @DorisBDR Apologies for the confusion, but on reflection I realise we cannot remove the client flags from the API function signatures in the way I previously described, so I won't try to change them in 2.7.6. I will still add a header to include mappings for other name changes (such as idamFree -> udaFree) and I'll commit those changes to this branch too. |
building pyuda wheels for windows and merging in upstream changes from main at release 2.7.6
@DorisBDR this should now be ready for testing |
…ug for double data in portablexdrlib for MSVC
i'm having two issues with 2.8.0
FYI [abadiel@ccs73n-1 mudaidamtrunk]$ replacing the code with the following two lines solved the issue in my case |
another issue is with the version |
I think the git archive will only show 2.8.0 as the version when we merge the PR and tag a new release. Was the version 2.7.6 exactly, or was it something like 2.7.6.XXXX? |
it was something like 2.7.6.XXXX |
OK this is expected behaviour until we tag the next release |
For the unrecognised command-line options I think it's a case of this: (ie warnings are only raised when there are other issues during compilation)
|
i have a doubt ...in this version shall we see systemd too? where and how it is managed |
ok i found these 2 files c/source/etc/uda@.service.in and c/source/etc/uda.socket.in i guess it is this one |
Yes that's right. I think the syntax for deploying the service is something like
|
Release targetting getting UDA to build on Windows CI runner