Update the screenshot.

Similar issue here: we have a 'MESSAGE' entity that stores message data, and online users may store up to around 1 million records at maximum. When using lightweight migration to add a new attribute to this entity, it takes a lot of time (about several minutes) and then results in Out Of Memory (OOM) crashes.

I suppose the Set here may refers to Set<Int> because you are adding code in the Set<Int> extension, the compiler are using the minimum scope of the defination. So try to use .init(array) or Set<String>(array) would be fine.