Evergreen | Most natural Swift logging

add ReCaptchaV3Service in provider

Based on the comments and the code, you've got a bit of a mess.

First off, your service should not have an @NgModule declaration: it's a service, not a module. Further, since your service isn't providedIn: "root", you need to actually provide it in your module.

Assuming AppModule is where this component and this service both live, you should have an app.module.ts something like this:

In your CartService, totalQuantity and totalPrice are subjects. So mock those subjects like this

There is no addDepartment(val:any) function in your SharedService class, this is one of those cases where error messages point to exactly the right place.

You're calling this.service.addDepartment(val) in the addDepartment() method of the AddEditDepComponent

karma-mocha-reporter would help you. It prints out the console logs before the expectations results. In this way, you can easily track which console message (including the error messages) was printed by each test.

Chris,

I haven't used linode or kong and don't know what your frontend actually does, so I'll just point out what I can see:

• The simplest dns check is to curl (or ping, dig, etc.):

  • http://[dataapi's pod ip]:80 from a host node
  • http://[kong-proxy svc's internal ip]/dataapi/api/values from a host node (or another pod - see below)

• default path matching on nginx ingress controller is pathPrefix, so your nginx ingress with path: / and nginx.ingress.kubernetes.io/rewrite-target: / actually matches everything and rewrites to /. This may not be an issue if you properly specify all your ingresses so they take priority over "/".

• you said 'using a kong ingress as a proxy to redirect incoming', just want to make sure you're proxying (not redirecting the client).

• Is chrome just relaying its upstream error from frontend-service? An external client shouldn't be able to resolve the cluster's urls (unless you've joined your local machine to the cluster's network or done some other fancy trick). By default, dns only works within the cluster.

• cluster dns generally follows [service name].[namespace name].svc.cluster.local. If dns cluster dns is working, then using curl, ping, wget, etc. from a pod in the cluster and pointing it to that svc will send it to the cluster svc ip, not an external ip.

• is your dataapi service configured to respond to /dataapi/api/values or does it not care what the uri is?

If you don't have any network policies restricting traffic within a namespace, you should be able to create a test pod in the same namespace, and curl the service dns and the pod ip's directly:

CoreWebView2.Settings.UserAgentis not supported in the current stable release (version 1.0.818.41). If you want to use CoreWebView2.Settings.UserAgent you must install the pre-release version, currently version 1.0.865-prerelease.

You can follow the directions here: To install a pre-release version

That also means that you must use Microsoft Edge CANARY build which you can get here: Microsoft Edge Insider Channels

Unfortunately, you might have to uninstall the 'WebView2 runtime' (which I think is a bug in the WebView2 package).

For anyone seeing this, seeing the same issue, the problem was with a constructor in a base component.

In the base component:

Thank you for contacting Syncfusion support.

We would like to inform you that currently, Syncfusion EJ1 components do not support Angular 11. We only have support till Angular 8. However, we have already logged a feedback to provide support for Angular 9. You van track its status from the below link.

Feedback: https://www.syncfusion.com/feedback/12334/provide-angular-9-support-for-ej1-components

However, as we have already lined up some major features, we could not implement this support immediately. We will implement this and include it in any of our upcoming releases. Please cast your vote on this feature based on the customer demand we will prioritize the features in our upcoming road map.

We would like to suggest our EJ2 TreeGrid component, which supports Angular 11. To learn more about EJ2-TreeGrid, please find the Online Documentation and Samples from the below links.

Documentation: https://ej2.syncfusion.com/angular/documentation/treegrid/getting-started/

Samples: https://ej2.syncfusion.com/angular/demos/#/material/treegrid/treegrid-overview

Regards,

Monisha.