From c5198418b018b336473590ff332ebe22eaf7dbdb Mon Sep 17 00:00:00 2001 From: Andrew Morgan Date: Wed, 6 Mar 2019 15:37:06 +0000 Subject: [PATCH] Use retry_after_ms instead of hardcoded delay --- .../views/settings/tabs/user/SecurityUserSettingsTab.js | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/components/views/settings/tabs/user/SecurityUserSettingsTab.js b/src/components/views/settings/tabs/user/SecurityUserSettingsTab.js index 02adeb1307..fdca4d169e 100644 --- a/src/components/views/settings/tabs/user/SecurityUserSettingsTab.js +++ b/src/components/views/settings/tabs/user/SecurityUserSettingsTab.js @@ -26,9 +26,6 @@ import Promise from "bluebird"; import Modal from "../../../../../Modal"; import sdk from "../../../../.."; -// Delay between failing invite acceptance/rejections to avoid rate-limiting -const INVITE_MANAGEMENT_DELAY = 10000; - export class IgnoredUser extends React.Component { static propTypes = { userId: PropTypes.string.isRequired, @@ -132,7 +129,7 @@ export default class SecurityUserSettingsTab extends React.Component { if (e.errcode === "M_LIMIT_EXCEEDED") { // Add a delay between each invite change in order to avoid rate // limiting by the server. - await Promise.delay(INVITE_MANAGEMENT_DELAY); + await Promise.delay(e.retry_after_ms); // Redo last action i--;