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
src/Data/Yaml/Config.hs:215:19:
1) Rollbar.Yesod.rollbarYesodMiddlewareWith, when there is an error, triggers a call to Rollbar
uncaught exception: ErrorCall
Could not convert to expected type: Error in $.token: parsing Token failed, expected String, but encountered Null
CallStack (from HasCallStack):
error, called at src/Data/Yaml/Config.hs:215:19 in yaml-0.11.11.2-72b012f81738f9aa8a0375a02116a9c2de7469091d3d770581aea04b4133eac8:Data.Yaml.Config
We found out a year ago or so that this is caused by an intentional limitation on GitHub Actions runners. Runners forbid using secrets in the CI of external PRs for security reasons (to avoid leakage and mishandling). Since we rely on a Rollbar token to run E2E tests, this means that the tests are failing.
We want to keep these E2E tests, so one potential solution would be:
Disabling the CI in external PRs coming from forks.
Asking external contributors to provide proof of tests passing when asking for review, or run the tests ourselves locally for external contributions, to ensure that they pass.
The text was updated successfully, but these errors were encountered:
On incoming PRs from forks, the tests fail:
We found out a year ago or so that this is caused by an intentional limitation on GitHub Actions runners. Runners forbid using secrets in the CI of external PRs for security reasons (to avoid leakage and mishandling). Since we rely on a Rollbar token to run E2E tests, this means that the tests are failing.
We want to keep these E2E tests, so one potential solution would be:
The text was updated successfully, but these errors were encountered: