This release does 2 things:
1) It adds the ability to add the package name that is calling the run limits to the message, which was a requested feature and will need porting into our other packages but this enables it.
2) It fixes a weird databricks bug that can happen when you try and array sort hundreds of nulls that leads to a java based error. I can't reliably reproduce it in the int tests without adding thousands of events so you'll have to take my word that it seems to consistently fix the issue by removing null-valued items from the sort first (these were removed by the array_join function later anyway so the result is the same). This should be more efficient and not cause the same issue.
I've done it in one big PR because it's was two tiny changes. None of these should be breaking so we can do a patch release which means that no other packages will need bumping. @emielver you should be able to easily rebase but I don't think it matters much.
Checklist
[x] I have verified that these changes work locally
[x] I have updated the README.md (if applicable)
[x] I have added tests & descriptions to my models (and macros if applicable)
Release Only Checklist
[x] I have updated the version number in all relevant places
Description & motivation
This release does 2 things: 1) It adds the ability to add the package name that is calling the run limits to the message, which was a requested feature and will need porting into our other packages but this enables it. 2) It fixes a weird databricks bug that can happen when you try and array sort hundreds of nulls that leads to a java based error. I can't reliably reproduce it in the int tests without adding thousands of events so you'll have to take my word that it seems to consistently fix the issue by removing null-valued items from the sort first (these were removed by the array_join function later anyway so the result is the same). This should be more efficient and not cause the same issue.
I've done it in one big PR because it's was two tiny changes. None of these should be breaking so we can do a patch release which means that no other packages will need bumping. @emielver you should be able to easily rebase but I don't think it matters much.
Checklist
Release Only Checklist