You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have a few hacks in our data import code for custom emoji to not assume that the user_profile_id field is set (and set author to None), because our Slack export tool doesn't have the data. Since Slack does show who uploaded custom emoji in their UI, it seems possible the data is available; we should try to get it and clean up the codebase.
The text was updated successfully, but these errors were encountered:
The s3 import code path made a hard assumption about `user_profile_id`
being set (we'd already fixed this in the local uploads code path).
Ideally, it should be, and I've opened #10268 for fixing that, but for
now this is how it needs to work.
The s3 import code path made a hard assumption about `user_profile_id`
being set (we'd already fixed this in the local uploads code path).
Ideally, it should be, and I've opened zulip#10268 for fixing that, but for
now this is how it needs to work.
We currently have a few hacks in our data import code for custom emoji to not assume that the
user_profile_id
field is set (and setauthor
to None), because our Slack export tool doesn't have the data. Since Slack does show who uploaded custom emoji in their UI, it seems possible the data is available; we should try to get it and clean up the codebase.The text was updated successfully, but these errors were encountered: