DomGarguilo commented on issue #6379: URL: https://github.com/apache/accumulo/issues/6379#issuecomment-4489703807
I agree with @dlmarion analysis here. The async call is kicked off then immediately the code checks the length of the current data which can definitely be the stale data since the async call probably hasnt completed yet. I think the best fix would be to move the logic that hides/shows the table into the DataTable setup. DatTables has a `drawCallback` option ([docs here](https://datatables.net/reference/option/drawCallback)) that I think would be the best place to move that code to. That would fix the bug. > However, looking at the tservers.js file as a whole, it does not appear to be using the data stored in the session storage. Instead it appears to be re-fetching from the Monitor server. This could take much longer and may cause the table to be hidden. I think this double fetching does exist and could be cleaned up but I am doubtful that it is causing any delays and I think its probably just the first async bug. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
