Mimic | Service Impersonator for Engineers | REST library

When you .catch() in a chain of promises, it means you already handled the error, and subsequent .then() calls continue successfully.

For example:

There's nothing in the SDK that would manage distributed transactions on your behalf. The simplest approach would likely be having a column in your database that allows you to mark when the event was published, and then have your function flow:

1. Write to the database with the "event published" flag unset; on failure abort.
2. Publish the event; on failure abort. (the data stays in written)
3. Write to the database to set the "event published" flag.

You'd need a second Function running on a timer that could scan your database for rows older than XX minutes ago that still need an event, which then do steps 2 and 3 from your initial flow. In failure scenarios, you will have some potential latency between the data being written and the event published or may see duplicate events. (Event Hubs has an at least once guarantee, so you'll need to be able to handle duplicates regardless.)

There is no callback response for port communication. However, you can mimic with a async wrapper that waits for a specific message. This will not just catch the recevier's reponse but all msg.subject that matches. However, with this, you can still do all your logic in one function rather than piecemeal in the listener.

I was playing with your code block. I have removed the content-type after this question answer.

I'm not that experienced with Vaadin Chart, but these are the questions that I can comment on:

(1) With 40x40 items you go over the threshold of 1000 in which the Chart switches into "turbo" mode for performance reasons. This seems to not be compatible with the heatmap series. You can disable turbo mode by setting plotOptions.setTurboThreshold(0);

(2) Unfortunately the ColorAxis doesn't support this, it only has an API for min and max color. Definitely a valid use-case though, and it seems to be supported by the Highcharts library that the Vaadin Chart uses under the hood. You should consider opening a feature request for this in the Github repo.

(3) This seems to be a documentation issue. The methods are available in later Vaadin platform versions, but not in 14.6.

(5) In theory not, but in practice there will be a huge performance hit in the browser due to the excessive amount of DOM elements (quick test of 100x100 froze the browser for 10s). I'm afraid the component isn't really made for such extreme use-cases. In this case it might be better to utilize a low-level JS drawing library using the canvas, or draw an image on the server-side and display that in the browser. Maybe you can also consider modifying your use-case so that you only display one slice of your data and allow the user to switch between slices.

I have tried something like this

The enter/exit pattern works when the data is an array of identified objects. Replace this code:

The message Set up the visualizer for this request is typical when the call to pm.visualizer.set() has been forgotten. But I did not forget it. So what is wrong?

As already touched upon, the problem is that Postman does not natively support promises. ¹
What does that mean? – Well, apparently it means that a function such as pm.visualizer.set() cannot be called from within the callback of a Promise. It has to be called from within the callback of pm.sendRequest(). Note that by the construction of the fetch() function the corresponding Promise is actually outside of the pm.sendRequest() callback!

In other words, you need to replace all occurrences of fetch() with pm.sendRequest().
You also need to implement your own version of Promise.all, since it relies upon promises, something you don't have in a native Postman script.
Fortunately, such an implementation was posted in an answer the day before yesterday.

After making those changes, here is the code for the Tests section, starting with the initializations: ²

Webpack changes __filename, so your attempt to go to the resource directory fails.

Add the following to webpack.config.js to leave __filename unchanged: