onetime | Ensure a function

I've been fine-tuning my client registration in IdentityServer 4.x and I've encountered a situation I cannot see a solution to.

First of, I'm implementing a strategy where I rotate my refresh tokens, so I set them to OneTime usage. In addition I set AbsoluteRefreshTokenLifetime to zero (0), and RefreshTokenExpiration to Sliding, with a SlidingRefreshTokenLifetime of e.g. 24 hours.

According to documentation this results in a configuration where the refresh tokens can be used only one time and when they are used they are getting a new expiration time.

when refreshing the token, the lifetime of the refresh token will be renewed (by the amount specified in SlidingRefreshTokenLifetime). The lifetime will not exceed AbsoluteRefreshTokenLifetime.

Also, mderriey has a nice explanation here which uses time-variables: https://github.com/IdentityServer/IdentityServer3/issues/2411#issuecomment-171483658

However, there is one statement that does not match what's happening on my side, and that is regarding the new expiration of the refresh token:

You use it at time T8 to get a new access token. Its new expiration time is T18

In my case the new expiration time is T22. The SlidingRefreshTokenLifetime is appended to how much time is remaining on the used refresh token.

So, I'm in a situation where I have configured my client, and every time a refresh token is used the newly created refresh tokens are getting increasingly longer and longer expiration times.

From the logs:

This is my code and I am wondering how I can get the sum of the calories of the meals the user inputted and output it to the user at the end.

Below you can see that where I commented in all caps for calCount. That doesn't work for my program and I believe I am wrong and that won't output the sum. Should I do the sum of calories before main() or in main()?

I can't wrap my head how to store / define the right model / relationship.

I have following data:

CATEGORY is their own model because i like to view / request in some situation only the category. But to this category I want set VALUE which I can only define onetime depending ON YYYY-MM.

What make me difficult to achieve / understand how i get the relationship between VALUE <-> YYYY-MM but still maintain the connection / dependency to only one CATEGORY "Rent".

now, I using radio button to render 2 components differently I use onClick with radio button to [isRepeat,setisRepeat] setState value

I have below JSON response.

From JSON response i am creating dynamic tab and inside every tab i want to push formArray based on below mentioned condition.

**In below response,

I have an app where user can scan details from his device and send details via https to my backend service so I can evaluate his data and send other data back to his mobile device.

Now I need to implement background task which would do previously mentioned scan once in a week, let's say on friday even when the application is not running. I don't want to send back to device any data if scan is run in background task not from user directly. I just need to send data from device to service.

I would like to choose the best solution which seems like WorkManager with periodic work request (https://developer.android.com/reference/androidx/work/PeriodicWorkRequest). However I have few questions.

1. Let's say I would like to make a scan every friday. Only constraint is that user has to be connected to the internet. If user install my application and execute it on monday I would set the repeat interval for 5 days and flex interval for 1 day. So background work should be executed last day which is friday. But after this background scan, period should change from 5 days to 7 days, so it can execute every next friday. How can I make this change? Should I run OneTime background work which run scan after 5 days and create repeated background task with 7 days period?

2. If user is not connected to internet all friday, is it gonna take another period (7 days in this case) since next execute or will it execute on saturday? If not on saturday, what should I do to run it on saturday?

3. If user is not connected to internet for half of friday, it is going to execute my background work on friday afternoon with 7 days interval and 1 flex day interval. However since the user wasn't connected for half day, next background work will be execute from friday afternoon to saturday midday? Or will it execute only in friday just like previous work? If not how can I prevent this behaviour?

4. If Work Manager can't ensure, that background task will be executed on friday, what should I use than. I think that one day is a quite huge interval and it shouldn't be such problem, right?

I am grateful for every opinion and advice.

I'm building a simple application using WPF and GalaSoft MvvmLight (5.4.1.1).
Everything works fine, I have a grid, and when a row is selected I enable/disable buttons that have actions assigned.

Sample button looks like that:

I'm developing a custom checkout and have a bit of trouble with the jQuery. What I want is for each item that's checked to be added to the Subtotal and the Total values. Also, when an item is unchecked, it is no longer added to the subtotal and total.

Currently, when I click on an option, it's added to the sub total and total values. However, when I UNcheck an item, it still adds again to the totals.

Here's the URL to the Pen I'm working in right now: https://codepen.io/BFrancoeur/pen/abyQJqj

What I've tried:

-- Unbind each event with .off(). This had no effect whatsoever on the totals -- Use .one() to limit each event to a single firing (or trigger). This didn't work, either. -- Create conditional (ternary) operators for each item and return sum += 0 when false. This had no impact on the results

What am I missing here? This is the only thing that's holding me up.

To view the code directly, see below.

Thanks!

I'm trying to create a precision timer. I found an example created with WinMM.dll. The sample works really fine. But it crashes with the first garbage collector.

How can I prevent the garbage collector from blocking the timer?