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
I had been using canvas.Image instead of image.Image in my code because the documentation mentioned possible decrease in encoding/decoding overhead. It worked for a long time, but I pulled a new version of this project while managing dependencies, and it started panicking telling me hash of unhashable type canvas.Image.
It seems to be a problem with embedImage using image.Image as a key in a map, but not expecting canvas.Image to be used in its place. I'm not sure what changed to break this, but it must be a library-side regression.
I changed my code to use image.Image and now it works exactly as intended.
I had been using
canvas.Image
instead ofimage.Image
in my code because the documentation mentioned possible decrease in encoding/decoding overhead. It worked for a long time, but I pulled a new version of this project while managing dependencies, and it started panicking telling mehash of unhashable type canvas.Image
.It seems to be a problem with
embedImage
usingimage.Image
as a key in a map, but not expectingcanvas.Image
to be used in its place. I'm not sure what changed to break this, but it must be a library-side regression.I changed my code to use
image.Image
and now it works exactly as intended.Full stack trace:
The text was updated successfully, but these errors were encountered: