After running the migration process once, the migration page fails to load #514

Closed
opened 2024-02-09 13:05:58 +01:00 by aumetra · 5 comments

I tried to migrate followers back to my original account after a little test phase, and after the process didn't fully complete after the first time, I wanted to re-trigger the migration.

Unfortunately when trying to open the migration settings, the page failed to load

image

And it seems like it's a bug when it attempts to load more user info (it passes an array of user IDs via the userIds property instead of a single user ID via the userId property)

image
image

I tried to migrate followers back to my original account after a little test phase, and after the process didn't fully complete after the first time, I wanted to re-trigger the migration. Unfortunately when trying to open the migration settings, the page failed to load ![image](/attachments/bf1e901f-8c2a-4c88-a3f5-3dd2fbbfe6b1) And it seems like it's a bug when it attempts to load more user info (it passes an array of user IDs via the `userIds` property instead of a single user ID via the `userId` property) ![image](/attachments/663b9d32-3d3f-475a-88f4-5805173de3b8) ![image](/attachments/7eeae9a7-a464-4b02-b02b-5838cac843f3)
Member

Can you write what steps have you done?

Can you write what steps have you done?
zotan added the
bug
more info needed
labels 2024-02-09 13:48:40 +01:00
Author

Sorry, sure. I first migrated from my Mastodon account over to Iceshrimp via the migration feature.

Then when migrating back to the same Mastodon account (since Mastodon allows reactivating your moved account), it worked just fine.
I simply entered the handle of the account and hit the button.

After reloading the tab, the page was blank and this error showed up in the JS console.


So in short the rough steps were:

  1. Add a Mastodon account as your old account handle in the migration settings in Iceshrimp
  2. Migrate over from Mastodon over the Mastodon settings
  3. Reactivate your Mastodon account in the Mastodon settings
  4. Start the process of migrating away in Iceshrimp and choose the same Mastodon account you originally migrated away from as the destination
  5. The page should be blank now

Edit:

The servers in question are corteximplant.com (which is running a modified version of glitchsoc; v4.3.0-alpha.1+glitch.cortex), and nightcity.bar (which is running Iceshrimp v2023.12.3)

Sorry, sure. I first migrated from my Mastodon account over to Iceshrimp via the migration feature. Then when migrating back to the *same* Mastodon account (since Mastodon allows reactivating your moved account), it worked just fine. I simply entered the handle of the account and hit the button. After reloading the tab, the page was blank and this error showed up in the JS console. --- So in short the rough steps were: 1. Add a Mastodon account as your old account handle in the migration settings in Iceshrimp 2. Migrate over from Mastodon over the Mastodon settings 3. Reactivate your Mastodon account in the Mastodon settings 4. Start the process of migrating away in Iceshrimp and choose the same Mastodon account you originally migrated away from as the destination 5. The page should be blank now --- Edit: The servers in question are corteximplant.com (which is running a modified version of glitchsoc; v4.3.0-alpha.1+glitch.cortex), and nightcity.bar (which is running Iceshrimp v2023.12.3)
zotan removed the
more info needed
label 2024-02-09 14:44:33 +01:00
Owner

Right, after inspecting the code this seems like a bug in the router, as the users/show endpoint that's being called here is configured to accept either of these

image

Right, after inspecting the code this seems like a bug in the router, as the users/show endpoint that's being called here is configured to accept either of these ![image](/attachments/263c0cb4-ff7b-41d3-af2b-c20d254da3fa)
159 KiB
Owner

ah! i see. the uniqueItems condition is getting you.

ah! i see. the `uniqueItems` condition is getting you.
zotan closed this issue 2024-02-10 15:52:53 +01:00
Owner

The latest dev commit should fix your issue. Thanks for reporting it!

The latest dev commit should fix your issue. Thanks for reporting it!
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: iceshrimp/iceshrimp#514
No description provided.