Now they are PendingRequests and we keep track of the nimsuggest instance that depends on it (when possible) and also the time it got triggered. The pending requests are shown in the extension status panel, later we will be using the active pending requests to determine if a given instance of ns is hanging so we can restart it without user intervention
Notice the Pending Requests (15) in the img above are there because the ls is not removing complete requests, but in a regular usage they shouldnt be there (we may introduce a toggle for debugging purposes that dont remove them when complete) or we could just show all and remove complete ones after certain period has passed since it was completed
Now they are
PendingRequestsand we keep track of the nimsuggest instance that depends on it (when possible) and also the time it got triggered. The pending requests are shown in the extension status panel, later we will be using the active pending requests to determine if a given instance of ns is hanging so we can restart it without user interventionNotice the
Pending Requests (15)in the img above are there because the ls is not removing complete requests, but in a regular usage they shouldnt be there (we may introduce a toggle for debugging purposes that dont remove them when complete) or we could just show all and remove complete ones after certain period has passed since it was completed