-
Notifications
You must be signed in to change notification settings - Fork 27
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
Bugfix #86
base: master
Are you sure you want to change the base?
Bugfix #86
Conversation
Sorry for the stupid title, I had to reload the page and it reset to my nondescript branch name ... |
Thanks @mbe-financial-com ! Looking good, we will try to test it asap. Could take a few weeks. |
@mbe-financial-com Sorry, but I can't merge this. We get the following error when running your version:
|
@willemdh But that line is from your version, introduced in 255e9b9!? I didn't change anything about that. Is that a very old Perl you're testing on? It should fail with the original HEAD, too. |
…ter- or node wide, fix filter to query only disks from home-node * add handling of spare disks in "shared" mode (partitioned or formated disks) these are logically not assigned to a specific nodes spare disk capacity so are shown at a _SHARED_ node and not shown in single-node mode * add a suboption "aggregate" that allows to sum up/aggregate all disks in the cluster (if run against a specific "node" the "shared" mode disks are accounted for the node) * fix query-building to find only disks for the specific home-node (the error was not visible before because it was post-filtered in result function) * fix broken branching conditions within these function (see also district09#86)
@mbe-financial-com Sorry it took me so long to test this. But it seems even with your latest commit, it still fails... |
@mbe-financial-com Do you still want to try resolve this, if so please resolve conflicts. Tx |
@mbe-financial-com Another pr merged, see #89 |
…ter- or node wide, fix filter to query only disks from home-node * add handling of spare disks in "shared" mode (partitioned or formated disks) these are logically not assigned to a specific nodes spare disk capacity so are shown at a _SHARED_ node and not shown in single-node mode * add a suboption "aggregate" that allows to sum up/aggregate all disks in the cluster (if run against a specific "node" the "shared" mode disks are accounted for the node) * fix query-building to find only disks for the specific home-node (the error was not visible before because it was post-filtered in result function) * fix broken branching conditions within these function (see also district09#86)
ae07462
to
3774e46
Compare
Did you test the version with the conflict marker?! Because that's the only way I could imagine how to get a compilation error on line 28. My version completely eliminates the whole smartmatch magic so the |
@mbe-financial-com I copied your version to my pr server and launched some checks, which failed with the error in the screenshot. As your pr failed 3 times yet, the moment I find some spare time I will first test and merge #90 |
@mbe-financial-com Hello, Just merged @Elias481 's PR. Can you rebase pls? Thanks. |
@mbe-financial-com Merged #91 rebase required if you still watn to see this merged. |
Hi,
I spent a few hours hacking on this check, resulting in the four commits here -- hope they're useful.
GetOptions()
was unnecessarily verbose, and there was a logic error in the option checking, leading to the "Use of uninitialized value $strOption" warning.defined($s && $s eq "foo")
instead ofdefined($s) and $s eq "foo"
. Even where they were, in this function I changed&&
to the unambiguously low-precedence logicaland
. Guess you'll want this, too.$strOption
. Now it errors out if the option is unknown, and does so in just over a quarter of the lines. I didn't bother with the Hungarian notation so I totally understand if you don't want this, or want to re-style it.get_*
function. May be useful, maybe not.I thought of adding support for
Monitoring::Plugin
as it would probably cut the LOC count in half and eliminate all the tedious status var juggling, but that would be too much for now ;)