I am experiencing issues with my DynamoDB datasource after an automatic upgrade to version 1.7.1 of my application. I am receiving a "for input string" error when performing Scan operations on my tables. I suspect this could be related to the upgrade and would like to know if anything could have broken the DynamoDB connector. The Appsmith team is treating this as a critical fix and providing updates on their Github page. They have suggested a temporary workaround of adding HTTP_PROXY and HTTPS_PROXY to the docker.env file and restarting the docker container. They have also requested API server logs and offered to schedule a session with their engineers.
The user is facing an issue with a DynamoDB datasource on their application after an automatic upgrade to version 1.7.1. The datasource Scan operation is failing with an error message stating "Execution failed with status 5000 For input string: ""." The user wants to know if this could be related to the upgrade and if anything could have broken the DynamoDB connector. The Appsmith team has confirmed that there is a bug related to DynamoDB and they are treating it as a critical fix. They have opened an issue on GitHub and provided a workaround solution for the user. The workaround involves adding the following to the docker.env file and restarting the docker container: HTTP_PROXY=http://:0 HTTPS_PROXY=https://:0. The team has also requested a session with the concerned engineers and asked for the API server logs to further investigate the issue.