Base page is replace by the first ressource loaded in HAR about chrome-har HOT 11 CLOSED

Hey @vroumvroum hmm I got the same in Chrome 66 and did this fix for that: #12

I wonder if it has changed in 67 too? Can you provide the full trace log in a gist, then I can have a look and see what's going on.

Best
Peter

from chrome-har.

Hey @soulgalore, is this what you are expecting : https://gist.github.com/vroumvroum/cda71d0c4e9efb22ced5eb4d5917b0e2 ?

from chrome-har.

@vroumvroum yep almost, anyway you could skip the puppeteer log and get the raw one? We got a couple of fixed coming up the coming days but the more logs that breaks, the better so we are sure we fix it.

from chrome-har.

from chrome-har.

Ah I see. In the example: https://michaljanaszek.com/blog/generate-har-with-puppeteer

// convert events to HAR file
  const har = harFromMessages(events);
  await promisify(fs.writeFile)('en.wikipedia.org.har', JSON.stringify(har));

Skip the conversion and store the raw events to disk, something like:

  await promisify(fs.writeFile)('en.wikipedia.org.json', JSON.stringify(events));

from chrome-har.

It would also be helpful if you could enable debug logging in chrome-har. Just set the environment variable DEBUG=chrome-har before running.

from chrome-har.

It's worth noting that the blog post linked to by the OP doesn't include the Page.frameScheduledNavigation event which is being handled as of #12

from chrome-har.

@soulgalore : here is the raw output of the events : https://gist.github.com/vroumvroum/3106072293a061040d498839e212dc42

@tobli : tried to generate har with DEBUG=chrome-har (output was empty)

@suever : I did tried to add Page.frameScheduledNavigation in the list of the events beforehand and it changed nothing ...

from chrome-har.

@soulgalore : if it is of any help, here is the raw events with Page.frameScheduledNavigation added on the observers list : https://gist.github.com/vroumvroum/fcb9200953e499e988819cbec3ee226d

from chrome-har.

Hi @vroumvroum!
It think your method of extracting Chrome DevTools Protocol events via Puppeteer isn't 100% at the moment. Events seem to be written out of order, which makes chrome-har not work. Comparing to the perflog dump that Browsertime generates (see https://gist.github.com/tobli/3d76c24911a6ab073fe5e6916d173c7b) you see that Network events (such as Network.requestWillBeSent) are printed before Page events (such as Page.frameStartedLoading) in your example.

It would likely be possible for the HAR building algorithm to work independently of event order, but it would require some non-trivial restructuring. If you'd like to dig into that we're definitely open to PRs. I'm closing this issue now, but you could open a new issue for discussing approaches to making the algorithm more "Puppeteer friendly". =)

from chrome-har.

Hi @tobli, @soulgalore : thanks for your help !
I will inform the author of this code.
For information, puppeter-har module (https://www.npmjs.com/package/puppeteer-har) is also based on the same code.

from chrome-har.