Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upIntroduce device id v2 #362
Conversation
109cdd6
to
275c5f2
fix test add comments
| return s3Helper.listNotifications( | ||
| this.sqs, notificationParams, category, prefix).then((values) => { | ||
| if (this.shouldRetireOldSQSQueue(parseInt(values.createdTimeStamp))) { | ||
| return this.deleteSQSQueue(this.oldSQSUrlByCat[category]).then(() => { |
This comment has been minimized.
This comment has been minimized.
darkdh
Dec 12, 2019
Author
Member
@AlexeyBarabash reminded me that when device id is duplicated, if there is an old Brave which doesn't contain the fix, its SQS queue will be unavailable until next relaunch because upgraded Brave deletes it after 24 hours
This comment has been minimized.
This comment has been minimized.
AlexeyBarabash
Dec 12, 2019
Contributor
I was confused and I thought this.deleteSQSQueue can delete queues belonging to other devices. And like @darkdh mentioned that only can happen if device id was duplicated. Which is a separate case.
This comment has been minimized.
This comment has been minimized.
darkdh
Dec 13, 2019
Author
Member
Non upgraded device will get reset anyway, so duplicate case won’t be an issue
|
++ |
|
Minor notice All the rest looks good. |
|
++ |
darkdh commentedDec 6, 2019
•
edited
fix #333
This PR introduce device id v2 which is a 3 random bytes hex encoded string.
We also keep device id for backward compatibility.
Migration from existing device would be:
SAVE_INIT_DATAfor updating device id v2