Spoke | Easily create custom 3D environments | Augmented Reality library

It looks like you are not using the on method correctly. According to the documentation it takes a single argument (the eventName) and returns an observable, which you can then subscribe to. It does not take a second argument as a callback.

That means you will need to change that first line to something like:

You need to obtain the device path using the SetupDi functions as shown in this answer.

I'd suggest you just take the code from inside of app.patch() and make it into a reusable function. Then it can be called from either the app.patch() route directly or from your other route that wants to do the same funtionality. Just decide what interface for that function will work for both, make it a separate function and then you can call it from both places.

For some reason (which I don't really understand, but seems to happen to lots of people), people forget that the code inside of routes can also be put into functions and shared just like any other Javascript code. I guess people seems to think of a route as a fixed unit by itself and forget that it can still be broken down into components and those components shared with other code.

Warning. On another point. This comment of yours sounds very wrong:

and then using app.set() to be able to use the req.body in another route

req.body belongs to one particular user. app.set() is global to your server (all user's requests access it). So, you're trying to store temporary state for one single user in essentially a global. That means that multiple user's request that happen to be in the process of doing something similar will trounce/overwrite each other's data. Or worse, one user's data will accidentally become some other user's data. You cannot program a multi-user server this way at all.

The usual way around this is to either 1) redesign the process so you don't have to save state on the server (stateless operations are generally better, if possible) or 2) Use a user-specific session (like with express-session) and save the temporary state in the user's session. Then, it is saved separately for each user and one user's state won't overwrite anothers.

If this usage of app.set() was to solve the original problem of executing a .patch() route, then the problem is solved by just calling a shared function and passing the req.body data directly to that shared function. Then, you don't have to stuff it away somewhere so a later route can use it. You just execute the functionality you want and pass it the desired data.

The PayPal-NET-SDK mention in comments is deprecated and should not be used. If you are going to make API calls for anything other than the Checkout-NET-SDK or Payouts-NET-SDK use cases, use direct REST API calls.

The best method to obtain a list of transactions is to download an activity log report in CSV format from www.paypal.com

However, if for some reason you require an API for this accounting task, the only publicly available one is the Transaction Search API: https://developer.paypal.com/docs/api/transaction-search/v1 -- which you must enable for the client ID you are using, and wait up to 9 hours (or terminate the token) if you have already requested an access token with it.

The best you can do is to parse each of the LogCleaner logs on the broker (meaning you need to de-dupe by topic and partition) to know when a segment on each broker is about to be removed

There's no way to know when individual messages will be deleted without dumping the log segments

In most applications, there's a true back-end that carries out operations on data (retrieving, modifying, deleting, adding). That true back-end has nothing at all to do with the presentation to the user. If it has an error, it should just report that error back to the presentation layer and then it's up to the presentation layer to know what the user context was and what is and isn't appropriate to communicate to the user.

The presentation layer can be entirely in the front-end or it may be a combination of back-end template rendering and front-end display. In any case, it is the presentation layer's job to display error messages to the end user in a form that fits the context and will make sense to the user. Sometimes this presentation will also include an error code (for use in more detailed bug reports and troubleshooting), but that error code will not, by itself, generally be useful to the user except for more detailed reporting of a problem.

So, there is no precise answer to front-end or back-end since sometimes the back-end is involved in rendering content for the front-end to display. Whatever layer is presenting information to the user (wherever that is) is what should be making an error message for the user.

If you then throw in language support where you have a front-end that can be displayed in many different languages, you can immediately see that you don't want your data managing back-end APIs to have to be responsible for rendering error messages in a whole bunch of different languages. That is clearly the responsibility of a separate presentation layer.

I rearranged the config file and it works now.

Working aws config:

Try this (untested):

Since you said both lists are in the same order, you can iterate them in parallel with zip: