On socket:
Gotcha. I'm looking forward to your update if you find something.
On sarning message:
Thinking of if it reported a problem or not, you can ignore the warning unless you want to use the reported backend (isal or shss) it appears when backend ".so" library not found at checking the existence. And IIRC, it will run only once when initialize the pyeclib module to check the backends availability. However, i thought Timur was working[1] to suppress the annoying message, though.
What liberasurecode version are you using? The liberasurecode is maintained separated as PyECLib so that you have to update also liberasurecode if you 're using older one.
On socket:
Gotcha. I'm looking forward to your update if you find something.
On sarning message:
Thinking of if it reported a problem or not, you can ignore the warning unless you want to use the reported backend (isal or shss) it appears when backend ".so" library not found at checking the existence. And IIRC, it will run only once when initialize the pyeclib module to check the backends availability. However, i thought Timur was working[1] to suppress the annoying message, though.
What liberasurecode version are you using? The liberasurecode is maintained separated as PyECLib so that you have to update also liberasurecode if you 're using older one.
1: https:/ /github. com/openstack/ liberasurecode/ commit/ c7a94df0724af30 b26e3856f9c1434 4fc9b73a09