Acid | A high speed C++17 Vulkan game engine | Game Engine library

In python you can use the Regex module (re):

If I understood your problem well, you can get it done by using 'input' function of python. This will enable you to give input from the CLI. Below is the modifies code.

Hope this helps you. Also if you want to avoid small/caps hedache for the input, you can use .upper().

Though its not required for this question.

You can add textposition = "none" to each trace so that it is only used in the tooltip.

Edit: Using hovertext instead of text and textposition = "none" (also see this related answer)

Just remove the concatenation (c) in group_by

plotly doesn't understand when back ticks are surrounding the variable name that it's still a column in the data. (With regard to the hovertext, specifically.) There are a few ways to get around this. Since you're still using the x and y of each trace, you can use hovertemplate instead.

updated

After I posted this answer I noticed that 2500 looked the same size as 4000 and that's not quite right. From there I recalled that plotly won't aggregate the totals. You can aggregate before or during, but it won't automatically sum the values.

Also, the function aggregate won't accept variable names in back ticks, either.

I've updated the code here to aggregate the totals so that your hovertext shows the total by group, not individual layers as you move your mouse down the column.

I added x and y labels in the call to layout, because the backticks were in the graph.

We may need to join (left_join) and then mutate to create the column

As there are inconsistent spaces between the digits and letter, we may use a regex lookaround

You should use a document with a state property in MongoDB, with possible values processing and done.

When a request comes in, try to insert the document into the database with the given idemKey and state=processing. If that fails because the key already exists, then either report success (if state is done) or that it is still being processed (if state is processing). Or wait for it to complete and then report success.

If inserting the document succeeds, proceed with executing "only-once logic".

Once the "only-once logic" is done, update the document's state to state=done. If executing the logic fails, you may delete the document from the database so a subsequent request can try to execute it again.

To protect against a server failure during executing the logic or against a failure to delete the document, you should record the start / creation timestamp too, and define an expiration. Let's say when a new request comes in and the document exists with processing sate but the document is older than 30 seconds, you could assume it will never be completed and proceed as if the document didn't exist in the database in the first place: set its creation timestamp to the current time and execute the logic, then update the state to done if logic execution succeeds. MongoDB also supports auto-removal of expired documents, but note that the removal is not timed precisely.

Note that this solution isn't perfect either: if executing the logic succeeds but you can't update the document's state to done afterwards, after expiration you could end up repeating the execution. What you want is the atomic / transactional execution of your logic and a MongoDB operation, which is not possible.

If your "only-once logic" contains multiple inserts, you could use insertOrUpdate() to not duplicate the records if the execution fails and you have to repeat it, or you could insert the documents with idemKey included, so you could identify which documents were previously inserted (and you could remove them first thing, or skip them and just insert the rest).
Also note that starting with MongoDB 5.0, transactions are supported, so you can execute multiple inserts in a single transaction.

See related question: How to synchronize two apps running in two different servers via MongoDB