We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I have encountered problems with the deployment workflow after updating the version of Flair incl. fixes in #440.
As seen in this workflow there's something wrong with tailscaled:
tailscaled
Run sudo tailscaled 2>~/tailscaled.log & sudo tailscaled 2>~/tailscaled.log & HOSTNAME="github-$(cat /etc/hostname)" until sudo tailscale up --authkey ${TAILSCALE_AUTHKEY} --hostname=${HOSTNAME} --accept-routes do sleep 0.5 done shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} env: pythonLocation: /opt/hostedtoolcache/Python/3.8.18/x64 LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.8.18/x64/lib TAILSCALE_AUTHKEY: *** failed to connect to local tailscaled (which appears to be running). Got error: Get "http://local-tailscaled.sock/localapi/v0/status": dial unix /var/run/tailscale/tailscaled.sock: connect: no such file or directory
I have started this workflow pipeline quite a lot over the past days, but the deployment was never successful.
This also happened in the workflow pipeline of timm, see here.
timm
Any help is highly appreciated!
The text was updated successfully, but these errors were encountered:
Unfortunately, I no longer can restart the GitHub workflow and it seems that the latest Flair fixes have not been yet deployed on the Model Hub.
Maybe @Narsil can have a look at this issue :)
Sorry, something went wrong.
No branches or pull requests
Hi,
I have encountered problems with the deployment workflow after updating the version of Flair incl. fixes in #440.
As seen in this workflow there's something wrong with
tailscaled
:I have started this workflow pipeline quite a lot over the past days, but the deployment was never successful.
This also happened in the workflow pipeline of
timm
, see here.Any help is highly appreciated!
The text was updated successfully, but these errors were encountered: