Open ZimM-LostPolygon opened 1 month ago
Kucoin and other connectors works on latest and using setup.sh
from deploy repo
Can you try again to reproduce the error then:
docker compose log backend-api
Thank you
There is no traceback. The only relevant line is the one I've already posted:
"POST /add-connector-keys/kucoin_test/kucoin HTTP/1.1" 400 Bad Request
I've tried 3 different machines, it's always the same error for me, both with docker-compose.yml
and docker-compose-dev.yml
Thanks for the response @ZimM-LostPolygon i will have a look if I can reproduce this issue this week
Looking at backend-api code though, there are only two places encrypt_secret_value
is mentioned:
And judging from the 'NoneType' object has no attribute 'encrypt_secret_value'
error, that means secrets_manager
is None 🤔 I can't think of any reason why that could be...
I thought about running backend-api
locally to debug it, but Conda activation always there as well on any of my machines, unfortunately.
Describe the bug
Trying to add credentials for any connector always fails. Standalone client works just fine with those same credentials.
Steps to reproduce bug
'NoneType' object has no attribute 'encrypt_secret_value'
error.In the
backend-api
container log, there's a line:"POST /add-connector-keys/kucoin_test/kucoin HTTP/1.1" 400 Bad Request
UPD: this happens with any connector, not just Kucoin