dotnet.github.io | The source for the dotnet.github.io site | Web Site library

I am trying to follow their tutorial for tests: Link to Orleans test docs

But the configuration shown is pretty simplistic:

This question is the same as this question. But the OP answered his own question and it didn't help me.

I am trying to create a documentation similar to the Docfx site:

However, when I build the project, I get the index.html that looks like this:

My configuration is this:

• Installed docfx.console as a nuget package in Visual Studio 2017 for the project.
• The version of docfx is 2.58.0.
• I'm building the project in Visual Studio, which produces the docfx output.

My folder configuration is:

Cannot get this to run. I get the following error message, I have made it as simple as possible but what required service am I missing.

I am using the Graph Type first approach. https://graphql-dotnet.github.io/docs/getting-started/introduction

System.InvalidOperationException: Required service for type autumn.TestOGT not found at GraphQL.Utilities.ServiceProviderExtensions.GetRequiredService(IServiceProvider provider, Type serviceType) in //src/GraphQL/Utilities/ServiceProviderExtensions.cs:line 33 at GraphQL.Types.SchemaTypes.<>c__DisplayClass7_0.<.ctor>b__2(Type t) in //src/GraphQL/Types/Collections/SchemaTypes.cs:line 141 at GraphQL.Types.SchemaTypes.AddTypeIfNotRegistered(Type type, TypeCollectionContext context) in //src/GraphQL/Types/Collections/SchemaTypes.cs:line 539 at GraphQL.Types.SchemaTypes.HandleField(IComplexGraphType parentType, FieldType field, TypeCollectionContext context, Boolean applyNameConverter) in //src/GraphQL/Types/Collections/SchemaTypes.cs:line 429 at GraphQL.Types.SchemaTypes.AddType(IGraphType type, TypeCollectionContext context) in //src/GraphQL/Types/Collections/SchemaTypes.cs:line 333 at GraphQL.Types.SchemaTypes..ctor(ISchema schema, IServiceProvider serviceProvider) in //src/GraphQL/Types/Collections/SchemaTypes.cs:line 154 at GraphQL.Types.Schema.CreateSchemaTypes() in //src/GraphQL/Types/Schema.cs:line 328 at GraphQL.Types.Schema.Initialize() in //src/GraphQL/Types/Schema.cs:line 102 at GraphQL.Utilities.SchemaPrinter.PrintFilteredSchema(Func2 directiveFilter, Func2 typeFilter) in //src/GraphQL/Utilities/SchemaPrinter.cs:line 79 at GraphQL.Utilities.SchemaPrinter.Print() in //src/GraphQL/Utilities/SchemaPrinter.cs:line 63 at Autumn.Api.Controllers.AutumnController.Schema() in C:\ws\Autumn-APICore\Autumn.Api\Controllers\AutumnController.cs:line 37 at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)

There is a couple of confusing points in the documentation that make me struggle to understand how exactly distribution across the cluster happens in Orleans. Hence, the questions.

Question #1

Orleans claims to have a built-in distribution capabilities to distribute across multiple servers. To me it sounds that Orleans can act as a load balancer itself and can scale out automatically. Thus, if I deploy Orleans app to several servers, then service discovery and load management should happen automatically, correct?

In this case, why some docs and articles suggest using other tools, like Ocelot or Consul, as a single entry point to Orleans cluster?

Question #2

I would like to use simple but distributed in-memory storage across several servers, like Redis or Apache Ignite, and I would like to know if it's possible to use a simple grain as this kind of a data storage?

Let's say, one grain will store a collection of restaurants and some other grain will keep track of the last 1000 visitors for selected restaurant. Can I activate these 2 grains only once as a singleton collection, add or remove records to each collection, and use these 2 grains as in-memory storage evenly available to all nodes in the cluster? Also, if answer is yes, do I need to add locks to these collections or each grain always exists in a single thread?

I am using GraphQL .net to respond to graphql queries on the backend of an Asp.net Core website. All the cookies seem to be passed with the requests but for some reason my graphql.net requests do not have the proper user session set on the HttpContext. The ClaimPrincipal is mostly empty via graphql.net while my Asp.net Core WebApi/Mvc style endpoints have the correct principal with user id even though both GraphQl.Net requests and non-graphql.net requests are happening at the same time.

I checked the payload and all the same cookies are passed in both requests. So it makes me wonder why are my regular WebApi endpoints able to (auto-magically) get the claims principal and why can't the graph.net endpoints do the same. As far as I know from previous usages of GraphQl.net I wasn't aware that any special session code had to be added (other than passing the user from the HttpContext to graphQL.net). I've been reading through GraphQL.Net and Asp.net core source code and docs, but so far I haven't found any obvious offenses or leads.

What might cause some issue like this? what are some common causes? Should I just try to figure out how to manually read in the cookie to Asp.net core and pull the principal?

Perhaps I'm missing a special header value? I don't think the headers are weird but I haven't done a side by side comparison between the headers in graphql.net and asp.net core requests.

In this snippet is where I first detect a problem. If I put a breakpoint here then the claimsprinical isn't correctly set for the current user session. And also later when I access the HttpContext the user session is not correct for graphql.net requests.

In GraphQL .Net most of the example code has one top level mutations graph object that has many actual mutations defined within it.
Here's an example from the GraphQL .NET mutations page:

Usually, it's recommended to create a wrapper implementing IHttpClient or IHttpClientFactory. Meanwhile, some Orleans samples show that it's ok to create HttpClient instance on-demand and use it directly from the grain.

Questions

• Should I create Orleans service as a wrapper around IHttpClient or call HttpClient directly from the grain?
• If I need a wrapper, would this implementation suffice?
• What's the difference between GrainService and GrainServiceClient?

For monitoring purposes, I need to log and measure every grain call (already available through Grain Call Filters), but also every grain activation/deactivation to have Grain Type counters, also for auto-scaling purposes.

I haven't found any global hooks besides Incomming and Outgoing grain call filters

Is there any way to get into the lifecycle of Grains in a global manner, besides the Incomming and Outgoing call filters?

I tried to start using DocFX and it meets my requirements, but I have a minor problem that is quite bothersome in the long run.

Every time I change something in the project and enable debugging, the DocFX's nuget adapts to the new changes.

This is correct behavior, but I would like to be able to turn this off for some time. It doesn't take long, but due to frequent changes it significantly extends the time to test anything.

I was looking in user Manual: https://dotnet.github.io/docfx/tutorial/docfx.exe_user_manual.html and I tried to do it on my own, but I didn't find any way to do that except to throw the nuget out of the project.