Re: NEW: comms/zigbee2mqtt [was Re: Node ports and specifically zigbee2mqtt]

pe 29.11.2024 klo 19.49 Stuart Henderson (stu@spacehopper.org) kirjoitti:

Please fetch a fresh zigbee2mqtt-1.41.0-vendor.tar.xz (if someone is
testing on a machine with net, make clean=dist is enough) and try this
instead.

Updated and now it is telling that it is progressing very slowly:

Let's see what happens after everything has had triple fail:

pm http fetch GET https://registry.npmjs.org/git-last-commit attempt 1 failed with ETIMEDOUT
npm http fetch GET https://registry.npmjs.org/humanize-duration attempt 1 failed with ETIMEDOUT
npm http fetch GET https://registry.npmjs.org/js-yaml attempt 1 failed with ETIMEDOUT
npm http fetch GET https://registry.npmjs.org/git-last-commit attempt 2 failed with ETIMEDOUT
npm http fetch GET https://registry.npmjs.org/humanize-duration attempt 2 failed with ETIMEDOUT
npm http fetch GET https://registry.npmjs.org/js-yaml attempt 2 failed with ETIMEDOUT
npm http fetch GET https://registry.npmjs.org/git-last-commit attempt 3 failed with ETIMEDOUT
npm http fetch GET https://registry.npmjs.org/humanize-duration attempt 3 failed with ETIMEDOUT
npm http fetch GET https://registry.npmjs.org/js-yaml attempt 3 failed with ETIMEDOUT
npm http fetch GET 200 https://registry.npmjs.org/git-last-commit 304160ms (cache stale)
npm http fetch GET 200 https://registry.npmjs.org/js-yaml 304125ms (cache stale)
npm http fetch GET 200 https://registry.npmjs.org/humanize-duration 304224ms (cache stale)

Best regards,

Hannu Vuolasaho