Skip to content
This repository has been archived by the owner on Sep 10, 2024. It is now read-only.

Check for devices with multiple access tokens during migration dry run #2244

Open
sandhose opened this issue Jan 8, 2024 · 2 comments
Open

Check for devices with multiple access tokens during migration dry run #2244

sandhose opened this issue Jan 8, 2024 · 2 comments
Labels
A-Migration Related to the migration tooling

Comments

@sandhose
Copy link
Member

sandhose commented Jan 8, 2024

Right now if a device has multiple access tokens on the same device, it fails on a unique constraint, and it does not warn about it during the dry run
@sandhose sandhose added the A-Migration Related to the migration tooling label Jan 8, 2024
@cleverer
Copy link
Contributor

cleverer commented Sep 2, 2024

Is this related to #2033 ? If so, has this been resolved with #2378?

@cleverer cleverer mentioned this issue Sep 2, 2024
Open
@matrixbot matrixbot mentioned this issue Sep 10, 2024
Open
@matrixbot
Copy link
Member

For your information, this issue has been copied over to the Element fork of matrix-authentication-service: element-hq/matrix-authentication-service#2244

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Assignees
No one assigned
Labels
A-Migration Related to the migration tooling
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sandhose @cleverer @matrixbot