Using the same index twice in a model file triggers an exception
degremont opened this issue · comments
With a Backend set (i.e. other than None), specifying the same index on two different OSTs triggers an exception.
This comes from the error message in the 'except' code block expecting an integer but getting a string.
Reported by: theryf
Please find a patch of this minor issue at the following location:
bullxpfs/lustre-shine@d869b2a
Thanks.
Original comment by: theryf
Thanks for the patch.
I made few minor changes to it and landed it.
Please note that it is always better to have a description in commit message, additionally to the subject. FYI I had the related comments to your patch.
Fixed in [a2c0ef]
Original comment by: degremont
- status: new --> closed
- Resolution: --> fixed
- Version: 1.3 --> 1.3.1
Original comment by: degremont