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
This seems to be a limitation with psycopg2 library used in Speckle Monitoring. This library is attempting to interpret the % as the start of a url-encoded character. In our case the following characters do not constitute a valid url-encoded character.
To Reproduce
See above description.
Expected behavior
Speckle monitoring can connect to a database without error, even when username and password include special characters.
Screenshots
Additional context
Proposed Solution (if any)
This is not a limitation with the node libraries, so it does not seem advisable to url encode the connection string at the point of input. Instead we should bring Speckle Monitoring's behaviour closer to that of the node libraries by url encoding the %.
Optional: Affected Projects
The text was updated successfully, but these errors were encountered:
What package are you referring to?
Monitor (for the postgres database)
Describe the bug
Given a Postgres connection string which includes a
%
in the username or password.Speckle monitoring will fail with:
This seems to be a limitation with
psycopg2
library used in Speckle Monitoring. This library is attempting to interpret the%
as the start of a url-encoded character. In our case the following characters do not constitute a valid url-encoded character.To Reproduce
See above description.
Expected behavior
Speckle monitoring can connect to a database without error, even when username and password include special characters.
Screenshots
Additional context
Proposed Solution (if any)
This is not a limitation with the node libraries, so it does not seem advisable to url encode the connection string at the point of input. Instead we should bring Speckle Monitoring's behaviour closer to that of the node libraries by url encoding the
%
.Optional: Affected Projects
The text was updated successfully, but these errors were encountered: