Richard Collette
Richard Collette
@qalinn - I have not found a workaround.
@qalinn The workaround I have used looks like: Gitlab build job ```yaml # BUILD build: stage: build interruptible: true extends: .kubernetes_runners
Totally agree with https://github.com/facebook/jest/issues/6527#issuecomment-505772215. Tests should stop running if `before...` has an exception/error. Your test setup conditions failed so how can you possibly run the expectations?
I wish we could at least create property accessors over the shadow properties of the the owned entity which should then allow the creation of an index using the index...
I've hit this with Chrome 129 as well. It only seems to be happening to me when running in headless mode so I have not been able to debug what...
Using the `clientContext: config.singleRun` option did not work for me and removing that setting entirely assuming that 16.2.16 was going to fix it, both did not work for me. The...
To provide some context about how this would drive traffic to Pact/Pactflow @YOU54F - The Angular team is [supposed to be replacing](https://blog.angular.dev/moving-angular-cli-to-jest-and-web-test-runner-ef85ef69ceca) Karma with the [Modern Web Test Runner](https://modern-web.dev/docs/test-runner/overview/) in...
My suggestion would be to create more of a system state api that can be used to fetch, validate and apply state in bulk, not unlike AWS CloudFormation. It's the...
Yet another workaround. Set the ID property using reflection ```c# private static readonly PropertyInfo? s_idAccessor = typeof(AppAndInstanceConditionEvaluatorAppOrInstance).GetProperty( name: "Id"); public static IdpDiscoveryPolicyRuleCondition CreateForUser(string mailAddress, string appId) { AppAndInstanceConditionEvaluatorAppOrInstance appInstance =...