Closed np-daxton closed 6 months ago
Hi,
I answered you by email but put the same answer here: Can you check you run the last version of the Gateway (1.7.0 currently). The Docker image automatically upgrades as there is no version number but that's not the case for the gateway. My guess is you have a mismatch between both versions of the code.
Tell me how it goes.
Cheers!
Hello @loicknuchel,
Thank you for your prompt response and the suggestions.
Yes, I am using the Azimutt Docker Image tagged as ghcr.io/azimuttapp/azimutt:main. Regarding the Gateway version, I am running it with Node.js version 18.19.1, and the Gateway version is 0.1.7. I have tried running it both from the GitHub source code and using the command npx azimutt@latest gateway, and in both cases, the version is 0.1.7.
Please let me know if there are any additional steps I should take or if there's a newer version of the Gateway I should be using.
Thank you once again for your help!
You were totally right, the values
attribute was wrongly added.
I fixed it in the 0.1.8
version, you can launch it with the latest tag: npx azimutt@latest gateway
Tell me how it goes.
Hello,
I've tested the updated version 0.1.8 and I'm happy to report that everything is now working perfectly. Thank you for the swift response and resolution!
Hello Azimutt Team,
I've encountered a couple of database validation errors when trying to connect my local database through the self-deployed Azimutt Gateway. Below are the errors:
Connecting to Local MySQL Error:
Connecting to Local Docker MySQL Error:
These errors suggest that there are invalid additional keys in the entity attributes which are not expected by the Azimutt schema validation.
Details:
Questions:
I appreciate any help or insights you can provide as I am keen to resolve these issues and successfully connect my database through the Gateway.
Thank you for your support!