Open ibraheemalayan opened 1 year ago
I made a PR to fix this a few weeks ago, try using this Docker image hash since there is no version cut with this fix:
zhenghaoz/gorse-master@sha256:026d1bd4ad3f861bb45be0d5f141bfe90ce244dfbefaf85a343dc0276a8100b0
That's the hash for gorse-master, you'll have to find one for gorse-in-one if you're using that.
cc @zhenghaoz Would it be a good idea to cut 0.4.15 with this fix?
Gorse version using the latest
gorse-in-one
docker image. ( 0.4.14 )Describe the bug I have no clue how it occurred, I sent a request for neighbouring items, the load balancer returned a
503 Service Unavailable
, after reviewing the container it was shutdown and the last logs contain the following:As you can see the error is mainly an
index out of range [-1]
Additional context It was working fine for about a week.
Using postgres as datastore, redis as cache store