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
As found by @aranhams, that error validation was introduced in Go version 1.16, as on changelog:
crypto/hmac
New will now panic if separate calls to the hash generation function fail to return new values. Previously, the behavior was undefined and invalid outputs were sometimes generated.
We believe therefore that the implementation of the hash generation function was already previously with an error, and only begin to break after the validation was introduced in the crypto library.
As a workaround, we fixed the Golang version utilized in the API Dockerfile as 1.15, in order to allow normal execution of the project.
This issue is open in order to better investigate this error, and perform all necessary changes in order to be able to execute the API in Go's latest version without errors.
The text was updated successfully, but these errors were encountered:
As discussed on #529 and #526, the api Dockerfile would throw the following error upon starting:
As found by @aranhams, that error validation was introduced in Go version 1.16, as on changelog:
We believe therefore that the implementation of the hash generation function was already previously with an error, and only begin to break after the validation was introduced in the crypto library.
As a workaround, we fixed the Golang version utilized in the API Dockerfile as 1.15, in order to allow normal execution of the project.
This issue is open in order to better investigate this error, and perform all necessary changes in order to be able to execute the API in Go's latest version without errors.
The text was updated successfully, but these errors were encountered: