• ⚠️Update Notice: Due to recent changes in the GSA API, we have updated the way iseq retrieves metadata. The metadata fetching process has been modified accordingly to ensure compatibility with the latest GSA API. Everyone please update iSeq version (≥ 1.9.8)

• New -Q, --quiet option: Added this option to suppress download progress bars. Useful when logging clean outputs.
• Fixed a bug where --database option failed to switch when ENA was inaccessible.
• If the MD5 check ultimately fails, delete the partially downloaded files.

• Fixed a bug when checking md5 of SRA files.

⚠️Update Notice
Due to recent changes in the ENA API, we have updated the way iSeq retrieves metadata. The metadata fetching process has been modified accordingly to ensure compatibility with the latest ENA API.

New -r, --protocol option to change the protocol only when downloading files from ENA.

• When using -e, --merge, create symbolic links or retain the original Run files to avoid re-downloading them after merging.
• Fixed the issue mentioned in #40: modified the behavior so that batch downloads do not terminate upon encountering an error, and instead continue until all items are processed.
• Added an error message when download failures occur, such as Download failures detected, please check fail.log for details.
• Fixed a bug where incomplete downloads from GSA were incorrectly reported as successful.

• Fixed the issue mentioned in #39. The problem was that using both -d sra and -g together would skip the MD5 check in vdb-validate.
• New -k, --skip-md5 option: Added this option to disable MD5 checks.

• Fixed a bug that occurred when re-downloading with empty metadata.
• Fixed a bug where the while loop exited abnormally with a non-zero exit code.

• Fixed the issue mentioned in #33. -s, --speed re-enable use.
• Fix the exception when the metadata file is empty, mentioned in #34
• Bug fix to resolve the issue of MD5 checksum failure when downloading ONT or HiFi third-generation sequencing gzip data.

Fix for [#27]: When downloading SRA files, the verification process gets stuck due to vdb-validate. This issue occurs because, starting from sra-tools version > 3.0.0, if vdb-validate is run without specifying the path to the SRA file, it attempts to re-download the file, causing the process to get stuck.

For example:
Running vdb-validate SRR931847 will hang, but vdb-validate ./SRR931847 will execute successfully.