-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
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
[BUG] Please authenticate via the warp client #109
Comments
This seems to be some race condition. I know from personal experience, sometimes the warp client says it's connected when it isn't actually connected. As a test, can you try to add a sleep before the Gotify job and see if that makes it better? |
Are you able to show the commands for the Gotify job? Looking at the logs, it seems that Gotify is having trouble detecting WARP as connected, as the "Please authenticate via the warp client" message does not seem to be from the warp-cli. |
Yeah! you can take a look at my actions here the one running warp-cli is called |
Your command seems to be a pretty straight forward curl call to your server, so I am not really sure why this is happening. I know I sometimes get failures as well when running tests for pull requests for this action, but they pass when I retry them, so the problem seems to be intermittent. Can you update your script to retrieve the warp debug logs, upload them as a GitHub artifact and see if you can find anything useful in them?
|
Okie! In the week I'll give it a shot and see whats going on :) |
Hey! I have 3 similar workflows that run at the exact same hour and ran the same workflow, which is a notification to a gotify server that I'm running, after setting up everything for some reason? Sometimes it works, and other times shows the
Please authenticate via the warp client
I am doing something wrong?
The text was updated successfully, but these errors were encountered: