Skip to content

This commit corrects the database connection logic in the `2-update_e…

Edouard Legoupil requested to merge feature-deduplicate-and-find-references into main_dev

Created by: Edouard-Legoupil

…mbeddings.py` script.

The previous implementation used SQLAlchemy's URL.create method and attempted to read the host and port from environment variables. This caused connection failures when used with a Google Cloud SQL Proxy, which requires connecting to localhost:5432.

The script has been updated to use the same connection string format as the other working scripts (e.g., 1-populate_knowledge_cards.py), which hardcodes the host and port to connect to the proxy correctly. This resolves the psycopg2.OperationalError and ensures the script can connect to the database.

  • Does my code meet the quality standards for releasing packages?
  • Does the reviewer have all the information to validate the features/issues without too much research?
  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports