Crux | Express API routing done right with a promise-twist | REST library

Ok, a rather specific question which requires additional explanation and context.

Context

We are POCing a "try-convert" from a bespoke language to .net core (5 currently) and blazor server. Server because it allows a try-convert scaffolding we can build security concerns round. The details of this are not important. It just explains why we have some constraints which may seem unrealistic under normal circumstances.

I am fully accepting that "no you can't" or even "no you shouldn't" is the likely outcome. We are exploring possibilities.

Question

The concept of a circuit in blazor is a really good fit for the presentation layer. We would like to store information at the scope of the circuit.

The obvious solution is to use a scoped service in the dependency injection container.

E.g. In my Startup.cs I can put

Good day, everyone. Hope you're doing well. I'm a Django newbie, trying to learn the basics of RESTful development while helping in a small app project. We currently want some of our models to update accordingly based on the data we submit to them, by using the Django ORM and the fields that some of them share wih OneToMany relationsips. Currently, there's a really difficult query that I must do for one of my fields to update automatically given that filter. First, let me explain the models. This are not real, but a doppleganger that should work the same:

First we have a Report model that is a teacher's report of a student:

I would like to create an array of pointers to arrays, which are dynamically allocated if/when my result is ready. The following code uses a type to get around being unable to set an array of pointers, but the function makeArray is always returning the same memory address.

The expected outcome would be different addressess, and thus separately controllable arrays. (I need to do this because I have very very large arrays that will be populated at random but must be ordered, and I don't want to preallocate a massive 2x2 array (order of 8GB) nor constantly reallocate and sort as new results come in, so my solution is preallocate a large 1x1 array that can have pointers to the 2nd dim, meaning I can place the pointer to the result in its correct "slot" if/when it becomes available)

I'm trying to work out why my JWT keeps expiring and the refresh doesn't appear to work, the crux of my code handling this:

On querying of Chrome UX Report API i get sometimes a 404 error, "chrome ux report data not found". Documentation says: If 404 - CrUX API doesn't have any data for given origin.

For all URLs I query, I get some metrics, there is no URL, where all metrics would be missed, and for most URLs I get all data.

But there are cases, where data of certain metric missed. For one URL is FID data missing (data for all other metrics exist), for another URLs - FID, LCP and CLS are missed (data for FCP exist).

Is it a kind of API glitch? What should I do to get data for all queried metrics?

PS: if i query the same URLs now and after 30 minutes, I get different results: for same URLs are different metrics data missed: at first query is FCP missed, at second query - LCP and CLS... Why is it so?

On the image you see how missed data looks:

I have to create a Dockerfile to copy certain zip files. Assume the files are

I've written some code that formats text. The code doesn't work if user has put the cursor in a shape that is part of a group of shapes, the solution for which is to ungroup the shapes.

I want to regroup the shapes after executing the formatting code.

I am able to store the underlying shapes as objects, as well as their names. But, the normal approach to grouping (using shape names) doesn't work, because there can be multiple instances of those shape names on a given slide. E.g. this doesn't work as there could be multiple instances of "textbox" on the slide:

I was answering one of the question related to Spring Security here on SFO. The user was not aware of the very basics i.e. PasswordEncoder bean, UserDetailsService bean. I explained the crux of things but couldnt refer him to the very basic of Spring Security from StackOverflow here. I faced the same myself while learning the basics and couldnt find consolidated basics for the same.

Considering the priority users give to SFO answers. I think I should add some info on basics of Spring Security on SFO myself. Answers from the community members are most welcome as well.

Edit: I have added my answer below.

In this question / answer from 5 years ago about logLik.lm() and glm(), it was pointed out that code comments in the R stats module suggest that lm() and glm() are both internally calculating some kind of scale or dispersion parameter--presumably one which describes the estimated dispersion of the observation values being predicted by the regression.

This naturally begets another question: if it's truly a real parameter being estimated by the fit algorithm somewhere (or even if it's just some kind of implicit / effective parameter), how do I access this parameter from the resulting fit object?

I've produced a MWE (plus supporting setup / plot code) below:

• Part 1 constructs some simulated input data, which we'll fit to a straight line (implying two fit parameters are expected). Given the question is about a hidden, internally modeled dispersion parameter, I wanted to make sure the fit algorithm is forced to do something interesting, so therefore 10% of the points have been deliberately modeled as outliers. If you understand what's shown in the plot below, then you can probably skip reading this portion of the code.

• Part 2 is the main body of the MWE, illustrating the point that my question is asking about: it runs glm() on the input data and examines some of the results, demonstrating that logLik() claims three parameter estimates, in apparent disagreement with glm() which seems to give two.

• Part 3 just produces a little supplementary figure based on the input data and results. It's only included for completeness & reproducibility; you can probably skip reading it too.