tailor | Cross platform photo booth project

For my UWP app, I'm trying to move some assets to my AppData folder. I'm surprised that I've seemed to lose the option of using qualifier names in the process.

For example, for the following pair of images

I am trying to connect the generated openapi-generator angular code with the JHipster CRUD views. I was trying to edit and tailor them together for the Pet entity, however, I get the following error:

"Argument of type 'Observable & Observable & Observable' is not assignable to parameter of type 'Observable'."

JHipster generates entities having models, services, and CRUD operations. The code generated by the OpenAPI generator has just service and model. I am trying to use the model and service from the OpenAPI gen in JHipster template. I have no idea what to change to remove the error. The code from the pet-update-component.ts, where I have problems with petService.updatePet(pet) and petService.addPet(pet):

I'm trying to write a vba code which will simplify the following kind of data:

by comparing the first 2 characters in a column heading so that only the one which contains data further down the column is kept. If there is no data in the column and the first two characters in the header are unique (in this case Ca and Cl) I would like to keep the column. The data set is always in alphabetical order so it should only have to look at the cells either side to check for a identical starting string. The simplification of the above table is shown below.

I think I can delete rows with identical duplicate headers using something like the bellow code, but I have no idea how to tailor it to the other criteria.

How can I change the minimum SDK in an Android (Studio) project with recent (2020+) versions of Android Studio and Gradle?

During the creation of a new Android Studio project the wizard ask for the minimum SDK required.

Since the wizard generates a lot of boilerplate files and code, I assume that the boilerplate code is tailored to the minimum SDK chosen. My first objective is to generate a modern, lean, forward-compatible (Kotlin) app, so I chose API 31 (most recent non-beta on 29 Dec 2021). However, once the app (which is simple) is working, I would like to lower the minimum SDK to include as many devices as possible (without adding legacy dependencies, code, etc.). Is this a correct way to think about the relation between the choice of minimum SDK and the boilerplate code?

There are existing questions on older (2013) versions of Android Studio (and Gradle), e.g. here, but these do not work in modern versions of Android Studio and Gradle (I have only one build.gradle file and it does not mention any SDK, adding this gives errors).

EDIT: see below an image of the folder tree, as suggested.

I have an ordered Python list of forms:

Need to make all the existing repos (around 30+) fault tolerant to deadlock and recover from it with log and wait approach.

Tried with success: I've answered below a custom SqlResiliencyPolicy using Polly after some research and tailored it to the project.

But, what I seek: The present way (PFB answered), demands me to either

1. Wrap all the existing DB calls with await _policy.ExecuteAsync OR
2. Provide custom overloads which accepts IAsyncPolicy param. and later call the intended method. Sort of extension to IDbConnection:

public static Task GetAsync(this IDbConnection connection, object primaryKey, IAsyncPolicy policy) => return await _policy.ExecuteAsync(async () => GetAsync (...));

In both ways, I need to change all my 30+ repos. But, is there a built-in way in dapper/some-other-approaches, where we can

"configure a Policy in startup and auto-magically all DB calls via dapper become resilient (fall backs to their fault tolerant mechanism) Similar to the ways of http clients resilience where policy is added while you register a client"

By this: will've code changes to minimum, need not touch repos but only the startup.

I've a below approach and sort of need an improvement over it.

The requirement for this arose in answering this question here which has only been partially completed, at least from my POV.

For all tables and data SQL + test harness, see the fiddle here.

I have a table and data as follows:

I am currently trying to unify my targets inside of my application. I have one codebase I build multiple versions of the app, all tailored to a different client using targets.

That said, I want to unify the build number and versions so when I write code and archive, all the apps are built with the same version/build numbers.

Can I have all the target plist files reference the main target plist for these numbers, so I do not have to go into each target and increment them?

Or should I have my appDelegate update its own target when archiving?

As of this morning, CircleCI is failing for me with this strange build error: