Open volkerjaenisch opened 2 years ago
@volkerjaenisch Thanks for reporting the bug. I will take a look at it when I have a chance. Of course PRs are very welcome if you would like to contribute a solution.
dear Sep!
Thank you for digging into this bug. I am handycapped by a montainbike accident and will (typing with left) not come up with a PR soon.
Cheers,
Volker
On 14.08.22 08:29, Sep Dehpour wrote:
@volkerjaenisch https://github.com/volkerjaenisch Thanks for reporting the bug. I will take a look at it when I have a chance. Of course PRs are very welcome if you would like to contribute a solution.
— Reply to this email directly, view it on GitHub https://github.com/seperman/deepdiff/issues/332#issuecomment-1214295203, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATL6SBZJMK6MCADTKEG473VZCG5XANCNFSM55MQOLBQ. You are receiving this because you were mentioned.Message ID: @.***>
oh, sorry to hear that. That sucks. I hope you will heal soon and be back on the bike.
Thanks for your wishes!
Your code is crucial for one of our really important customers. Currently this bug is not surfacing in development, but in one of our tests. And to be true it was not the test but an error in the test that triggered the 0-d-array.
So this may be a corner case never surfacing. I thought it a good idea to mention it - for your completeness.
So keep your hair on and do not rush. And enough of left hanf typing for today.
Cheers,
Volker
Message ID: @.***>
I am also hitting the same issue while trying to calculate DeepHash of an model object during training.
Until a formal fix is released, is there is a quick hack that I could apply on my side to solve this issue @seperman ?
I do like DeepDiff/DeepHash really!
But today I think I found an error:
Expected behavior A hash should be created
OS, DeepDiff version and Python version (please complete the following information):
Additional Context DeepDiv also behaves weird with 0-d-arrays
Cheers, Volker