invoker | awesome utility to manage all your processes in development

Yes, the exception occurred due to firewall. The ping test is successful from local machine to VM but not from VM to local. I contacted the organization network administrator to confirmed this.

public WebDriver driver;

This declares a field, named driver. Not sure why you made it public.

WebDriver driver = new ChromeDriver();

This declares a local variable, also named driver, which is completely unrelated to the field you declared. As all local variables go, it ceases to exist when the method you declared it in ends. Because it has the same name, referencing variable driver in this method refers to the local variable and not the field.

All you really wanted was to make that second line:

You are violating the JPA spec by accessing the persistence context in a lifecycle listener.

See the JPA Specification 4.2 Section 3.5.2

In general, the lifecycle method of a portable application should not invoke EntityManager or query operations, access other entity instances, or modify relationships within the same persistence context. A lifecycle callback method may modify the non-relationship state of the entity on which it is invoked.

"a portable application should not" is the specification way of saying: Don't do that, anything might happen. Maybe the world ends.

The fix is not to do that. Maybe be preloading the currently logged in user and reference it so you may access it in your entity listener and do not set a reference to the user, but simple store its id or similar.

Ingress internal means "Accept only the requests coming from the project's VPC or VPC SC perimeter".

When you use API Gateway, you aren't in your VPC, it's serverless, it's in Google Cloud managed VPC. Therefore, your query are forbidden.

And because API Gateway can't be plugged to a VPC Connector (for now) and thus can't route the request to your VPC, you can't use this ingress=internal mode.

Thus, the solution is to set an ingress to all, which is not a concern is you authorize only the legit accounts to access it.

For that, check in Cloud Run service is there is allUsers granted with the roles/run.invoker in your project.

• If yes, remove it

Then, create a service account and grant it the roles/run.invoker on the Cloud Run service.

Follow this documentation

• Step 4: update the x-google-backend in your OpenAPI spec file to add the correct authentication audience when you call your Cloud Run (it's the base service URL)
• Step 5: create a gateway with a backend service account; set the service account that you created previously

At the end, only the account authenticated and authorized will be able to reach your Cloud Run service

All the unauthorized access are filtered by Google Front End and discarded before reaching your service. Therefore, your service isn't invoked for nothing and therefore your pay nothing!

Only API Gateway (and the potential other accounts that you let on the Cloud Run service) can invoke to the Cloud Run service.

So, OK, your URL is public, reachable from the wild internet, but protected with Google Front End and IAM.

The error message already gives you some hint here:

System.NotSupportedException: The collection type 'Newtonsoft.Json.Linq.JObject' is not supported. at System.Text.Json.JsonPropertyInfoNotNullable`4.GetDictionaryKeyAndValueFromGenericDictionary(WriteStackFrame& writeStackFrame, String& key, Object& value)

As you can see, there is some Newtonsoft.Json.Linq namespace, and a System.Text.Json namespace.

Starting with ASP.NET Core 3.0, the default serializer for JSON was changed from Newtonsoft.Json to the new serializer that is built into .NET Core: System.Text.Json. There is very detailed documentation on the differences between these two serializers and how to migrate your code to System.Text.Json. But the summary here is that System.Text.Json is—by design—more limited than Newtonsoft.Json and it will not be able to serialize directly from or to those JObject or JArray objects.

Fortunately, for applications that rely on the behavior of Newtonsoft.Json or otherwise require some of its flexibility, there is a way to reconfigure the ASP.NET Core application to continue using Newtonsoft.Json for JSON serialization.

To do that, you can follow the migration guide for ASP.NET Core 3.0. Essentially you will have to reference the NuGet package Microsoft.AspNetCore.Mvc.NewtonsoftJson and then call AddNewtonsoftJson() on the MVC builder in your ConfigureServices method. For example:

It will be fixed with the upcoming Spring-data-jdbc 2.3.x. Relevant issue 974 has been closed.

That specific error is coming from your stockPortfolio getter, specifically, this line:

Since you have the value returned by the Arduino in a variable, you can use it in your If statement:

To replicate this in Blazor, you'll need to hook into the Component Lifecycle events and use a bit of JSInterop.

Create a js file to hold your own initialization code