kate-nightly@8629: download via aria2 failed

[edisoncks]

Updating 'kate-nightly' (8548 -> 8629)
Downloading new version
Starting download with aria2 ...
Download: Download Results:
Download: gid   |stat|avg speed  |path/URI
Download: ======+====+===========+=======================================================
Download: 498b21|ERR |       0B/s|C:/Users/kurai/scoop/cache/kate-nightly#8629#f7f06d2.7z
Download: Status Legend:
Download: (ERR):error occurred.
Download: aria2 will resume download if the transfer is restarted.
Download: If there are any errors, then see the log file. See '-l' option in help/man page for details.

ERROR Download failed! (Error 3) Resource was not found
ERROR https://cdn.kde.org/ci-builds/utilities/kate/master/windows/kate-master-8629-windows-cl-msvc2022-x86_64.7z
    referer=https://cdn.kde.org/ci-builds/utilities/kate/master/windows/
    dir=C:\Users\kurai\scoop\cache
    out=kate-nightly#8629#f7f06d2.7z

ERROR & 'C:\Users\kurai\scoop\apps\aria2\current\aria2c.exe' --input-file='C:\Users\kurai\scoop\cache\kate-nightly.txt' --user-agent='Scoop/1.0 (+http://scoop.sh/) PowerShell/7.4 (Windows NT 10.0; Win64; x64; Core)' --allow-overwrite=true --auto-file-renaming=false --retry-wait=2 --split=5 --max-connection-per-server=5 --min-split-size=5M --console-log-level=warn --enable-color=false --no-conf=true --follow-metalink=true --metalink-preferred-protocol=https --min-tls-version=TLSv1.2 --stop-with-process=10224 --continue --summary-interval=0 --auto-save-interval=1

Please try again or create a new issue by using the following link and paste your console output:
https://github.com/ScoopInstaller/Versions/issues/new?title=kate-nightly%408629%3a+download+via+aria2+failed

[github-actions]

You are right. Thank you for reporting.

Following URLs are not accessible:

• The remote server returned an error: (404) Not Found. (https://cdn.kde.org/ci-builds/utilities/kate/master/windows/kate-master-8629-windows-cl-msvc2022-x86_64.7z)

[aliesbelik]

Seems to be up-to-date and accessible.

Please keep in mind that autoupdate action runs every 4 hours (in case of versions bucket) so gap in several hours between published release and corresponding manifest update is possible.