resets

Then I tried to switch to PAE paging by: unset PG -> set PAE -> write to %cr3 -> set PG and I succeeded. But I want switch to PAE paging directly. How is that possible?

It's not possible.

If "plain paging" is already in use/enabled, then you can't atomically enable PAE and load CR3 at the same time, so (regardless of whether you load CR3 first then CR4, or load CR4 first then try to load CR3) whichever instruction happens first will make the CPU crash before the second instruction is fetched.

The only way is to temporarily disable paging.

As you mentioned in the github issue, it looks like the root cause of your issue is that the reset action takes place asynchronously, and so hasn't gone through yet by the time you try to set the time.

One way to get around this is to define your own async function which resets the stopwatch, then waits for the action to complete before returning:

You can make generator in various ways

inline

As noted in comments - you need to account for your Find not getting a match:

Grouped by 'userID', create a new group based on the occurrence of 1 in 'purchase' by doing the cumulative sum on the lag of 'purchase', then create another grouping based on the difference in adjacent 'date' values i.e. checking if the difference is greater than or equal to 10 days, do a cumulative sum, and summarise the 'sessionID' by pasting (str_c), get the first element of 'date' and last of 'date' and any value of 1 in 'purchase' as summary columns

You have to rename it inside change_table if you want it to work as you are using it now.

The question then is, how do we get the workers to share and operate on the same object?

While you could share objects via something like multiprocessing, in your use case you're probably better off using a cache, like Redis.

I'm no expert at all in parallel/concurrent applications, but I do know that unless you need to speed up really expensive CPU-bound operations (i.e. very complex and/or long runnning calculations), you DO NOT want to share objects between processes.

You CAN do that, via dedicated libraries and modules, however it will make your app significantly more complex, having to handle all the possible race conditions and edge cases intrinsic with parallelism. If you do want to go that route, I'm sure there are plenty of libraries and tools, but you should first take a look at multiprocessing, the standard python library for handling parallelism. Check also this and this about using it to share resources among workers with gunicorn.

On the other hand, your use case doesn't look like it requires very complex calculations, so I would suggest to use a simple cache to act as the "data hub" for your workers, instead of a class. It will give you the desired result of having a single source of truth for your processes without the complexities of shared memory.

If you want to give this approach a try, I suggest to give a look at Redis which is a very popular and well supported solution for a cache and can even persist the data if you want.

Here's a list of Redis clients for python. redis-py is the recommended one.

As a side question, the problem above affects the /reset endpoint too. If this endpoint is called then only one of the workers will reset its object. Is there a way to force all workers to respond to a single call on an endpoint?

If you use a cache the problem disappears. You only have a single source of truth and you just erase the data there, with whichever worker responds to the request. Then every worker will see the data has been reset.

See https://github.com/microsoft/vscode/issues/120004 if you are using macOS or linux. It is a known issue which may already be fixed. There are a couple of proposed user fixes to try until the new Stable build is out later this week.

See the issue for more info but you could try setting your

terminal.integrated.letterSp[acing to 1 to see if that fixes it for you in the meantime.

You can find the index of last row of a group using shift and boolean operations like so

Code: