STR: - Open google.com with netmonitor open - Check that some of the requests don't have any status code. Expected: All requests should have some status code Actual: Some of the requests especially cached ones, don't have any status code associated and the status code is undefined. Check attachment

I can't reproduce this on my machine (win10) Ricky, do you see the problem? Honza

I can reproduce it on my machine definitely. Some cached network requests don't expose cached status value, so it causes this problem.

Hi Ricky, I'm interested in working on this issue. Can you give me some pointers on how I can get started on this?

Hey Abhinav Hoppula, Thanks for your interest! This issue seems not to appear in high frequency and barely reproducible. But it actually happens intermittently when navigating webpage like go forward / go back, and to make it worse it's not only status column but also other columns have affected (sometimes type, transferred, size columns are missing). In short, fixing the problem might be not as easy as we think. I suspect that those missing values are related to follow-up onNetworkEventUpdate [1] event. Corresponded response data doesn't update to UI properly. You might need to insert log around this code path to see what happens here. [1] https://searchfox.org/mozilla-central/source/devtools/client/netmonitor/src/connector/firefox-data-provider.js#366

Hi! If Abhinav isn't on this anymore, I'd like to give it a try! After a few tests, it seems like this is happening randomly and I can't figure out a pattern for this bug. At first I thought it was only appearing on some cases when the monitor showed up a "cached" request, but then I wanted to take a screenshot and show it in this bug's attachments, and it happened also without being next to a "cached" request. It is not only the status that is not appearing but also the "Transferred Size". Which shows "0GB".

Hi Kevin, This issue is unassigned. Please feel free to give it a try.

Cool, thanks Abhinav! For now, I do not have any clue of how to solve this issue, I tried to put some console.log to understand what is happening with no success. I'll investigate more tomorrow

Hi, I am pretty stuck on this. I tried to understand how the firefox-data-provider.js is working. I figured out that when information is missing from the network monitor, it seems to be coming from some eventUpdate that are missing (like 'responseStart') But until now I couldn't find out where the problem is coming from really, even bt looking down through the call stack... Ricky, do you have any clue on this?