Skip to content

CRC32 checksums are stripped of leading 0 #175

@WackerO

Description

@WackerO

Hey there,

I just used qpostman list --user=iivow01 --with-checksum --password QDAPA* to go over the resulting checksums of the project (I ran the command on cfc) and noticed that some entries do not have the same checksum as when calculating directly on cfc. Specifically, it seems that the checksums that begin with a 0 are shortened; the following output:

# Dataset         NGSQDAPA055A5 (20240508101711441-1254188)
# Source          QDAPA055A5
# Registration    2024-05-08T08:17:11.759797Z
# Size            2.47 GB
  2.47 GB       586e9d1 QDAPA055A5_BR995ZX01010010_good_2.fastq.gz
 44.00  B       355b908c        QDAPA055A5_BR995ZX01010010_good_2.fastq.gz.origlabfilename
107.00  B       9f661dcf        QDAPA055A5_BR995ZX01010010_good_2.fastq.gz.sha256sum
  8.00  B       3053d4a5        source_dropbox.txt

displays for QDAPA055A5_BR995ZX01010010_good_2.fastq.gz the checksum 586e9d1 when according to crc32 QDAPA055A5_BR995-ZX01-010010_good_2.fastq.gz it is 0586e9d1.

Best,
Oskar

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions