GetRecommendations | sample android application that uses the Audience Network

Here's what happens:

1.) The components unmount.

2.) Effect cleanups happen (directly afterwards, synchronously), and abortController.abort(); gets called. From now on no setState shall be called on the component.

3.) Either fetch(...) or res.json() (?) throw the exception, and the Promise gets rejected

4.) In a microtask, the .catch callback runs, and setError and setIsLoading get called. As the component does not exist anymore, the error you see is raised.

In my eyes cleaning up the fetch should be silent, so AbortErrors should be supressed:

The only problem with your query is that you are escaping the '$network_userid' like a string but you should do: @Query("MATCH (n {id: $network_userid }) RETURN n") without the string literal indication.

In general it's done at this point for very basic recommendations.

Since you are using PutEvents call, then all of the real-time events are added to Interactions dataset this way. Interactions datasets created by manual import and by PutEvents calls are separated from themselves. You can actually see them in Personalize Datasets web console.

Still you might want to update dataset files, using dataset import job feature, but it's going to replace your existing dataset. In general I would recommend using it only when:

• You just created a fresh/bigger/better dump of your database with Interactions.
• You've found, that your previous interactions dataset was invalid.
• The schema of dataset changed (pretty much you are forced to do it then).
• User or Item dataset changed/improved, it's actually a good idea to refresh it often, so Personalize can produce better recommendations. Keep in mind, that it also requires retraining of the Solution, so the new Items/Users will be included during the recommendations generation.

So for interactions you usually don't want to update dataset. For other datasets it might be a good idea to even create an automatic import mechanism.

Keep in mind, that Items and Users datasets are used only with Personalize Recipes, that support metadata. Otherwise they are simply ignored.

That's a common problem when working with Angular. Your content is updated so Angular has no choice but to destroy it from the dom, and create it again, losing track of the item.. Hopefully, solutions exist !

I would advice you to use trackByFn https://netbasal.com/angular-2-improve-performance-with-trackby-cc147b5104e5

This answer also explains really well what it does and how to use it https://stackoverflow.com/a/45391247/10265078

Array split() makes things very easy...

browser.storage.local.get returns a promise that is executed asynchronously. The function that contains your return statement is executed after the rest o the block of code and can not have any influence of the execution of the rest of this block. You will need to place the rest of the block in a function and change the code to

The short answer to your question is that there isn't a way to do exactly what you want.

The longer answer about why that is not available is in the FAQs:

Firstly, it is assumed that you have control over the provider's data (and consumer's data) when doing the verification tests. If you don't, then maybe Pact is not the best tool for your situation.

Secondly, if Pact supports making an assertion that element $.body.name may be present in a response, then you write consumer code that can handle an optional $.body.name, but in fact, the provider gives $.body.firstname, no test will ever fail to tell you that you've made an incorrect assumption. Remember that a provider may return extra data without failing the contract, but it must provide at minimum the data you expect.

The same goes for specifying "SOME_VALUE or null". If all your provider verification test data returned nulls for this key, you might think that you had validated the "SOME_VALUE", but in fact, you never had. You could get a completely different "SOME_VALUE" for this key in production, which may then cause issues.

The same goes for specifying an array with length 0 or more. If all your provider verification data returned 0 length arrays, all your verification tests would pass without you ever having validated the contents of the array. This is why you can only specify an array with minimum length 1 OR a zero length array.

Remember that unlike a schema, which describes all possible states of a document, Pact is "contract by examples". If you need to assert that multiple variations are possible, then you need to provide an example for each of those variations. Consider if it's really important to you before you do add a Pact test for each and every variation however. Remember that each interaction comes with a "cost" of maintenance and execution time, and you need to consider if it is worth the cost in your particular situation. You may be better off handling the common scenarios in the pact, and then writing your consumer to code to gracefully handle unexpected variations (eg. by ignoring that data and raising an alert).

https://docs.pact.io/faq#why-is-there-no-support-for-specifying-optional-attributes

Here's how to get recommendations based on seeds.