paranoid | Paranoid buildscript | Browser Plugin library

Looks like that vulnerability is in Logback, which is a dependency that's only used in the unit tests (further down that page you screenshotted shows the different dependency categorizations).

I need get that updated, obviously, but it doesn't impact the library itslef.

First you need to change your aggregate that you call once for every Album to an annotation, this will remove all of those extra aggregation queries

As you are concerned about the speed to load the objects, There is another way to improve performance. Like there are a number of methods we can use

• ModelSerializer (Slower)
• Read Only ModelSerializer (A little bit faster than ModelSerializer)
• Regular Serializer Read Only
• regular Serializer (almost 60 % faster than ModelSerializer)

Because In the writable ModelSerializer, a lot of time is spent on validations. So we can make it faster by marking all fields as read-only.

A lot of articles were written about serialization performance in Python. As expected, most articles focus on improving DB access using techniques like select_related and prefetch_related. While both are valid ways to improve the overall response time of an API request, they don't address the serialization itself.

And Yes you should go for multiple serializers instead of a BIG NESTED ONE

So by default the session strategy is set to jwt, which means your session is encoded / signed and safe to store sensitive info in.

However, NextAuth.js can be used to automatically put that accessToken you get from your OAuth provider in the JWT token via the jwt callback. Therefore you can pull it out anywhere with the getToken() method you mentioned and authenticate against Google APIs for further use (get drive contents, contacts, etc, etc, etc).

Check out this example for how to do that in the jwt callback: https://github.com/nextauthjs/next-auth-refresh-token-example/blob/57f84dbc50f30233d4ee389c7239212858ecae14/pages/api/auth/%5B...nextauth%5D.js#L67

what about a clumsy admin that's accidentally deletes everyone ?

• You can demonstrate how you have restricted Admin access into a Production AAD B2C directory. You can demonstrate that you fully orchestrate your directory configuration through CI/CD pipelines with gated deployments through multiple AAD B2C tenants that act as lower environments.

• You have 30 days to restore all deleted objects.

• Nobody can delete all accounts via the Portal, and nor should there be any CI/CD pipeline built to perform such an action.

And Azure AD B2C stores much more than user data.

1. User object - Dump users via Graph API. ObjectId can not be restored in the case of permanently deletion by an Admin.
2. Application Registrations - Config should be in a repo and controlled with CI/CD. If permanently deleted, you should demonstrate how to rebuild an App Registration using the config from your Repo, and update the Application code to reflect the new ClientId/ClientSecret. ClientId cannot be restored from a permanently deleted Application Registration.
3. User Flows - Config should be in a repo and controlled with CI/CD
4. IdP Configurations - Config should be in a repo and controlled with CI/CD
5. Custom policies - Config should be in a repo and controlled with CI/CD

Generally all features that you've configured have MS Graph API configurable endpoints that you can manage via CI/CD, and maintaining these configs in a repo.

Like the documentation says:

The frame_clause specifies the set of rows constituting the window frame, which is a subset of the current partition, for those window functions that act on the frame instead of the whole partition.

Now array_agg acts on the frame (it aggregates all rows in the frame), while lead doesn't. The documentation goes on to explain:

The default framing option is RANGE UNBOUNDED PRECEDING, which is the same as RANGE BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW. With ORDER BY, this sets the frame to be all rows from the partition start up through the current row's last ORDER BY peer. Without ORDER BY, this means all rows of the partition are included in the window frame, since all rows become peers of the current row.

So the presence of ORDER BY changes the meaning of the default frame of the window.

I suppose you need to indicate field option in associations along with name:

You are using Survey's mixin but missing scope in Survey's association.

Found a not-so-elegant but working way of doing it. It's not as easy to manually set updatedAt as with user-defined columns, and the afterDestroy and beforeDestroy hooks require save() or update() to be able to actually make changes - guess they weren't really designed with being able to update fields in mind.

Solution was: