webui | new web interface for configuring and viewing FlexGet | User Interface library

First make sure you have the correct packages in the same project as the context. You will need the following.

microsoft.aspnetcore.diagnostics.entityframeworkcore microsoft.entityframeworkcore.sqlserver

Also make sure you are using a hard coded options builder connection in your context rather than the name parameter like below. Just remember to change it back before publishing your changes.

Looks like you found an phosphor-webui openbmc recipe issue.

The text "Attempting to disable network" comes from here which was changed 8 days ago by this. So lets check upstream to see if there is a fix in review. I don't see any changes to open bmc recipes here

You should be able to do one of three things

1. remove phosphor-webui from you image, and build without it. Just remove phosphor-webui from you machine conf, and use webui-vue instead.
2. Roll you openbmc repo back 18 days and build before it the breaking change. git checkout ca2f10c
3. Fix the recipe and make everyone's life better. It looks like you need change the Datastore Variables. Something like d.setVar(network, "true") in the recipe file. (if that works send in a patch)

Discord and eMail are the perfered ways of reaching out to the openbmc community. Let us know how it goes and if you have anymore issues.

Posting the answer out of comments.

First what kubectl proxy is:

Creates a proxy server or application-level gateway between localhost and the Kubernetes API server. It also allows serving static content over specified HTTP path. All incoming data enters through one port and gets forwarded to the remote Kubernetes API server port, except for the path matching the static content path.

Also kubectl proxy works with HTTP requests, it does not work with TCP traffic. (this is probably the reason why it did not work).

You can read more in a good answer - kubectl proxy vs kubectl port-forward

Common options to access the service inside the cluster are:

• use kubectl port-forward - for local development and testing purposes

• use loadbalancer or nodeport service type - more advanced options which can be used across clusters and production environments. Find more about service types.

Blazor can talk with javascript through Microsoft.JSInterop.IJSRuntime. You can create a javascript function in your index.html to show Gantt, then call it from your blazor code.

Here is an example. I simply implement the example from https://github.com/jsGanttImproved/jsgantt-improved.

First, in you index.html, include jsgantt css and js, and prepare a function to be called from blazor. It is kind of an api exposed to blazor to show Gantt. I assume you save jsgantt files under wwwroot/content folder.

You need to implement a custom validator. When you implement a Custom Validator, you can decide the logic and it can be implemented in both server-side and client-side. And ASP.NET validation infrastructure takes care of validating it along with the other validators.

Here is the doc which talks about implementing custom validation

Here is one example - https://stackoverflow.com/a/15975880/38024 which will help you. Or you can use external nuget packages like ExpressiveAnnotations

You only specified an English localization file: Shared.en.resx.

When you specify @loc["countries"] in the component, it attempts to use the browser locale to translate the text "countries".

The localizer looks for a resource file Shared.de.resx but that doesn't exist, so it defaults to the base translation, in this case English.

For logging from custom keywords, you can use KeywordUtil.logInfo() method, as described in documentation.

For more info, you can check the Katalon forum.

Thanks to the comment by Cerise

The application parses all of the template files to one template set. The "content" template in test.html is the last "content" template to be added to the set. That's the one you see for each page. Parse the template for each page to a separate set.

So, here the correct working code

I solved it by fixing the static route as: