-
Notifications
You must be signed in to change notification settings - Fork 309
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-33057 Allow attributes for implicit storage planes to be merged #19364
base: master
Are you sure you want to change the base?
Conversation
Jira Issue: https://hpccsystems.atlassian.net//browse/HPCC-33057 Jirabot Action Result: |
This will need rebasing/reviewing after #19362 is reviewed/merged. |
@jackdelv please can you convert this to a normal PR and retest it with the most recent version of the platform. |
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.
please can you convert this to a normal PR and retest it with the most recent version of the platform. Then re-tag me for review.
Signed-off-by: Jack Del Vecchio <jack.delvecchio@lexisnexisrisk.com>
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.
Most changes look reasonable.
system/jlib/jfile.cpp
Outdated
@@ -8045,7 +8046,7 @@ static PlaneAttributesMapElement *findPlaneElementFromPath(const char *filePath) | |||
for (auto &e: planeAttributesMap) | |||
{ | |||
const char *prefix = e.second.first.c_str(); | |||
if (prefix) // sanity check, but should never be null | |||
if (isEmptyString(prefix)) // sanity check, std::string cannot be null, so check if empty |
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.
Test has been inverted. Should be !isEmptyString()
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.
@jakesmith we should have some unit tests to catch problems like this. Not quite sure how to code them easily though.
Type of change:
Checklist:
Smoketest:
Testing: