Event type unsupported randomly triggered
See original GitHub issueOur organization has been using GitHub actions heavily for about a month, we just ran into this a bit ago today during one of our release deployments of our platform.
##[error]Event Validation Error: The event type release is not supported. Only push, pull_request events are supported at this time.
##[warning]No scopes with read permission were found on the request.
##[error]Node run failed with exit code ***
This is from the actions/cache, is it possible you have seen this before or if this was recently changed? We have been using this for weeks without any issue until just about an hour ago, even earlier today it was fine.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Troubleshooting Amazon EventBridge - AWS Documentation
If events still don't match after a short period of time, check the CloudWatch metrics TriggeredRules , Invocations , and FailedInvocations for your...
Read more >What Does The "Unsupported event received on socket ...
This error occurs if a client event has been triggered and the name of the event is not allowed. Client events must have...
Read more >Event | Google Chat
Represents information about the user's client, such as locale, host app, and platform. For Chat apps, CommonEventObject includes information submitted by ...
Read more >onchange event on input type=range is not triggering in ...
When I played with <input type="range"> , Firefox triggers an onchange event only if we drop the slider to a new position where...
Read more >Troubleshoot form issues in model-driven apps - Microsoft Learn
The most common cause of intermittent or random form errors is using unsupported client API methods. These errors have the following ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@wipe2238 Apologies for the breaking change, I’ll get this fixed. For a workaround, you can add an
if
statement to check the event name and conditionally run the cache Example:👋 Hey @smeijer, please see https://github.com/actions/cache/issues/208#issuecomment-596664572
There’s a known issue that re-runs of Pull Requests can’t read from the cache