Keyvan Mosharraf

Hi Till, we have been using your code to retrain our solutions on personalize for while now. Very easy to use and works right out of the box. Now we...

`--stack-name` would do the job! Glad it's possible. In our use case, most of the parameters would remain the same. We are looking to train two different datasets with different...

Perhaps to avoid checking out the repo twice, you can add a feature like determine which `params.cfg` file to use from env variables? If you think this is a useful...

Trying to run make with the second stack name. While the stack in cloudformation gets created with the new name, it seems like the Lambda functions retain their name, which...

> It seems that setting `FunctionName` in https://github.com/aws-samples/amazon-personalize-automated-retraining/blob/master/stack.template#L125 (there is one occurence for each function) is unnecessary and will generate a random, unique name if not set. So removing all...

@Till--H Wow yes that's what I was thinking. Amazing that it's possible

For me just doing `npm i -D @mdx-js/react` did the job. Didn't need to pin the version nor add `overrides` to package.json

I'm having the same issue in create-react-app. Perhaps using inline source maps in the library would mitigate this issue? I had a similar problem while building a library recently, and...

This is my solution so far, a combination of the snippets in this thread. Big thanks and credit to everyone: ```python class ProxyAwareHistoricalRecords(HistoricalRecords): # inspired by https://github.com/jazzband/django-simple-history/issues/544 def _find_base_history(self, opts):...

Thanks @vigo, I'm gonna check your new project out!