You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per the screenshot below, the test is failing on a forked repo.
Expected behaviour
Test should pass just like the repo from upstream.
Screenshots / Live demo link
Additional context
No response
@ruchernchong don't worry; that action is a double-check that the APIs work when a change is deployed to Vercel. It only matters if you are doing development and want to merge a change into the upstream. More importantly, in this case, the Wakatime API timed out. This happens from time to time. The problem will likely go away when you re-run the action.
As per the screenshot below, the test is failing on a forked repo.
Expected behaviour
Test should pass just like the repo from upstream.
Screenshots / Live demo link
Additional context
No response
@ruchernchong don't worry; that action is a double-check that the APIs work when a change is deployed to Vercel. It only matters if you are doing development and want to merge a change into the upstream. More importantly, in this case, the Wakatime API timed out. This happens from time to time. The problem will likely go away when you re-run the action.
Describe the bug
As per the screenshot below, the test is failing on a forked repo.
Expected behaviour
Test should pass just like the repo from upstream.
Screenshots / Live demo link
Additional context
No response
The text was updated successfully, but these errors were encountered: