You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ops.help in matching failure can cause infinite loop #187
I think that the best idea here would be to change that call to run env.helpVerbose(), which does not attempt to simplify (in the current design). I think it has the added benefit of jumping straight to the verbose information, which the user probably wants anyways if matching didn't work, but I'd defer to @elevans' opinion on that one.
I just talked to @gselzer about this and I agree that using env.helpVerbose() here instead of env.help() 1) results in an ideal output for this scenario and 2) allows us to bypass this for now.
Activity
hinerm commentedon Feb 23, 2024
In this particular case, separating the ops arbitrarily by priority avoided the infinite loop
gselzer commentedon Feb 23, 2024
I think that the best idea here would be to change that call to run
env.helpVerbose(), which does not attempt to simplify (in the current design). I think it has the added benefit of jumping straight to the verbose information, which the user probably wants anyways if matching didn't work, but I'd defer to @elevans' opinion on that one.elevans commentedon Feb 26, 2024
I just talked to @gselzer about this and I agree that using
env.helpVerbose()here instead ofenv.help()1) results in an ideal output for this scenario and 2) allows us to bypass this for now.Use helpVerbose instead of help for failed matches
gselzer commentedon Feb 28, 2024
Fixed with scijava/incubator#129