-
Notifications
You must be signed in to change notification settings - Fork 304
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
HPCC-32963 Fix ecl unused-files for bare-metal roxie with TLS and custom port #19291
HPCC-32963 Fix ecl unused-files for bare-metal roxie with TLS and custom port #19291
Conversation
Jira Issue: https://hpccsystems.atlassian.net//browse/HPCC-32963 Jirabot Action Result: |
@@ -117,6 +117,10 @@ void CWsDfuXRefEx::init(IPropertyTree *cfg, const char *process, const char *ser | |||
throw MakeStringException(-1, "No Dali Connection Active. Please Specify a Dali to connect to in you configuration file"); | |||
} | |||
|
|||
#ifndef _CONTAINERIZED | |||
initBareMetalRoxieTargets(roxieConnMap); |
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.
It seems like there is another
void initBareMetalRoxieTargets(MapStringToMyClass<ISmartSocketFactory> &connMap, IPropertyTree *serviceTree, const char *daliAddress)
in ws_ecl_service.cpp - could these be commoned up ?
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.
OK yes you're right- I'd copied that function from ws_ecl_service.cpp into TpWrapper for HPCC-31394 and missed the common-up. Should I common up in this ticket or in the parent (HPCC-32962) where I'll roll out the fix to the other services?
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.
I've added a note to HPCC-32962 to common-up that code.
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.
ok
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.
Just one question
And why did some of the CI tests not pass ?
…tom port In non-containerized deployments, fix the `ecl roxie unused-files` command to work when roxies are configured for TLS (SSL) and/or they're using a nonstandard port other than 9876. Signed-off-by: Terrence Asselin <[email protected]>
7a259e6
to
5dc7b23
Compare
Not sure, looks ECLWatch/npm related something with OTel. I've rebased to see if I pick up some fix from target. And it looks like the tests now pass. |
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.
Looks ok.
@ghalliday ready to merge |
Jirabot Action Result: |
In non-containerized deployments, fix the
ecl roxie unused-files
command to work when roxie is configured for TLS (SSL) and/or is using a nonstandard port other than 9876.Type of change:
Checklist:
Smoketest:
Testing:
Passed manual tests:
ecl roxie unused-files
command was able to communicate with roxie, no errors.ecl roxie unused-files
command continues to work for native protocol using port 9876.Other occurrences of this issue, including for containerized code will be addressed in ticket HPCC-32962