synchronic | Automatically exported from code.google.com/p/synchronic

I'm having trouble understanding control flow with asynchronous programming in JS. I come from classic OOP background. eg. C++. Your program starts in the "main" -- top level -- function and it calls other functions to do stuff, but everything always comes back to that main function and it retains overall control. And each sub-function retains control of what they're doing even when they call sub functions. Ultimately the program ends when that main function ends. (That said, that's about as much as I remember of my C++ days so answers with C++ analogies might not be helpful lol).

This makes control flow relatively easy. But I get how that's not designed to handle event driven programming as needed on something like a web server. While Javascript (let's talk node for now, not browser) handles event-driven web servers with callbacks and promises, with relative ease... apparently.

I think I've finally got my head around the idea that with event-driven programming the entry point of the app might do little more than set up a bunch of listeners and then get out of the way (effectively end itself). The listeners pick up all the action and respond.

But sometimes stuff still has to be synchronous, and this is where I keep getting unstuck.

With callbacks, promises, or async/await, we can effectively build synchronous chains of events. eg with Promises:

I'm trying to get all the documents from all the collections from a firestore database which looks something like this:

I seem to be encountering some kind of synchronicity issue. In the head of my pages, I am loading in a navigation intoa

I am making a project with electron and SQLite and I came across a problem with synchronicity.
after searching I came up with the following solution but I wonder If I can turn the following promises into async/await pattern

I would like to send the data by chunks now what i'm sending to the server look like this for loop - 1, 2, 3 what the server receives: 3,1,2 -> asynchronous. and i need to send it synchronic so the server will receive as my for loop order: 1, 2, 3 How can i do it ?

UPDATE: @jfriend00 below said what I'm attempting to do is impossible, which I would have known if I knew had asynchronicity worked. Which I still technically don't. 😂 But they proved to me that I need to reverse the project out further to run my function sooner or redo it entirely at a higher level than the "scope" I was trying to run my function in. 🤦‍♀️

This is kind of long but I'm at my wits end and need any kind of opinions from anyone. I always figure things out by using StackOverflow, I never use. So, just now, I'm desperate. And it seems to be something super commonly misunderstood but I have to ask about my specific situations since no solutions on the internet have helped me solve the problem.

I'm working on a mostly-open-source project called Cloudron (https://git.cloudron.io/cloudron/box/-/blob/master) and this is my first time working on a Node project. And I'm having the hardest time setting a variable and having it be available by the time I need it.

Having issues understanding asynchronous-ness in the context of this large a project that seems to use callbacks, which I also don't see how they will help because this variable needs to be set. I've read a ton of articles and a RIDICULOUS amount of stackoverflow problems / answers (and that's never failed me before). Stuff about Promises and callbacks and I try them and nothing I've experimented with actually waited for the variable to be set by my new function (I even wrote a setTimeout hoping that would just force it to wait and nothing really waited).

Anyway, to the meat of the actual problem - I added my new function to this project in src/docker.js:

I have page that is uploading multiple file to individual Google Signed URLs.

My files_to_upload variable is an array of file from my input. I then loop through these and call my upload function for each.

My upload function first fetches a signed URL generated from my own php script and then uploads the file to that URL.

When this happens I can see that the files are different the first time I log them but the last time I log them they are the same file which is the last one in the array.

Files get uploaded to separate URLs but the last file is uploaded to both of them.

There is definitely a synchronicity issue but I am unsure how to resolve this.

In VSCode when I add the await keyword before an update in a transaction, the word await is underlined and when I scroll over it I see the message "await has no effect on the type of this expression. ts(80007)"

Is this message correct? If so, could updates in transactions cause any synchronicity issues?

I'm not actually using TypeScript in my app, but I suppose the message still could be relevant.

In case it helps, here's the full code of the transaction. It's a poker app and the goal is to make sure that when multiple players join a table at the same time it doesn't try to add more players than allowed to the table.

In this example : https://data.wort.lu/tests/css/curved.html the baskets are following the wheel... except on Firefox.

It seems like FF does have a problem with keySplines as attribute to animateMotion.