add non-ascii connection string tests

[osaxma]

I was taking a look at #38 but I could not reproduce the issue (actually I remember facing issues with @ symbol a while back as well but I could not reproduce that either).

Anyway, I've already added tests for passwords using non-ASCII characters for the three supported auth methods by the package -- namely:

• clear password
• md5
• scram-sha-256

All of them pass (won't work on the CI though as each test needs its own pg_hba.conf to be mounted).

They might be useful to keep if you think so. -- I believe they are necessary based on the next comment.

[osaxma]

Actually, the error is reproducible if you change the pubspec.yaml deps to:

dependencies:
  buffer: ^1.1.0
  crypto: ^3.0.0
  collection: ^1.15.0
  sasl_scram: '0.1.0' # <~~~~ pin here

In this version, both md5 and scram-sha-256 tests would fail with the following error:

PostgreSQLSeverity.fatal 28P01: password authentication failed for user "abc@def"

In my local pubspec.lock, the version was 0.1.1 which had the issue fixed already..

When #38 was filed (and when I experienced issues with @ symbol) , 0.1.1 was not published yet.

See:

• cannot connect to database with password that contains an ü (u-umlaut) mongo-dart/sasl_scram#1 (comment)

[isoos]

I haven't really checked yet, but IIRC Github Action is able to run docker run and other commands... have you tried it?

[osaxma]

Yeah I believe it's possible but not with the current setup (e.g. using services.postgres)... I'll give it another shot later and try a different setup.

[isoos]

Note: a repository can have multiple workflows, and we can differentiate tests either via directory or tags.

[isoos]

(Also: thank you for looking into this!)

[osaxma]

Yeah that what I was thinking -- to tag tests with a solo tag and exclude them from common tests and then run all solo tests with concurrency=1.

[isoos]

Thank you for the continued work here! I'll just merge this and we can figure out how to run it on Github actions later.