Store a MD5 hash of content for stored messages · python-discord/metricity@6fc204b

Triggered via pull request September 10, 2024 15:36

jb3

opened #187

Status Failure

Total duration 37s

Artifacts –

main.yml

on: pull_request

5 errors and 1 warning

Ruff (D400): alembic/versions/a192a8d3282c_add_content_hash.py#L1

alembic/versions/a192a8d3282c_add_content_hash.py:1:1: D400 First line should end with a period

Ruff (D415): alembic/versions/a192a8d3282c_add_content_hash.py#L1

alembic/versions/a192a8d3282c_add_content_hash.py:1:1: D415 First line should end with a period, question mark, or exclamation point

Ruff (S324): metricity/exts/event_listeners/_syncer_utils.py#L36

metricity/exts/event_listeners/_syncer_utils.py:36:16: S324 Probable use of insecure hash functions in `hashlib`: `md5`

Ruff (COM812): metricity/exts/event_listeners/_syncer_utils.py#L46

metricity/exts/event_listeners/_syncer_utils.py:46:39: COM812 Trailing comma missing

Process completed with exit code 1.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/