Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DevTools Error: Unsupported time zone specified undefined #6046

Closed
brunoxd13 opened this issue Sep 18, 2018 · 17 comments
Closed

DevTools Error: Unsupported time zone specified undefined #6046

brunoxd13 opened this issue Sep 18, 2018 · 17 comments

Comments

@brunoxd13
Copy link

Initial URL: http://localhost:3000/
Chrome Version: 69.0.3497.92
Error Message: Unsupported time zone specified undefined
Stack Trace:

RangeError: Unsupported time zone specified undefined
    at new DateTimeFormat (native)
    at Date.toLocaleTimeString (native)
    at new Audits2.ReportSelector.Item (chrome-devtools://devtools/bundled/audits2/audits2_module.js:242:460)
    at Audits2.Audits2Panel._buildReportUI (chrome-devtools://devtools/bundled/audits2/audits2_module.js:184:28)
    at Audits2.Audits2Panel._startAudit (chrome-devtools://devtools/bundled/audits2/audits2_module.js:192:181)
@wardpeet
Copy link
Collaborator

wardpeet commented Sep 18, 2018

I believe @paulirish is the best man to answer this. I don't know the devtools pipeline about lighthouse.

the issues seems to be here https://cs.chromium.org/chromium/src/out/Debug/gen/devtools/audits2/audits2_module.js?q=_buildReportUI&sq=package:chromium&dr=C&l=242

edit(paulirish): unminified, it's coming from here.

@paulirish
Copy link
Member

@brunoxd13 thanks very much for reporting. this is quite interesting.

what operating system are you running this on?

this bug indicates your system doesn't know what time zone it's configured for. do you know if a time zone is set in your OS settings?


to team: we also hit this back here and fixed it on the LH side in #1067. I guess we need to try/catch it everywhere.

@paulirish
Copy link
Member

Ah this appears to be this upstream bug: https://bugs.chromium.org/p/chromium/issues/detail?id=364374
It is fixed in Chrome, so Chrome Canary shouldn't be a problem.

@brunoxd13 if you want to try again with Chrome Canary, please let us know if it's fixed there.

@brunoxd13
Copy link
Author

@paulirish @wardpeet I was able to solve the problem, it was my GTM configuration that was in manual mode, so I put automatic worked. Thaks a lot.

@wardpeet
Copy link
Collaborator

@brunoxd13 oh so we could easily reproduce this with gtm?

@brunoxd13
Copy link
Author

@wardpeet I believe that manually changing.

@paulirish
Copy link
Member

@brunoxd13 whats GTM? google tag manager?

@brunoxd13
Copy link
Author

@paulirish I believe that @wardpeet meant gmt, not gmt. Is it ok?

@wardpeet
Copy link
Collaborator

Hehe sorry I thought you meant Google tag manager TBH 🙈. It was weird that gtm would mess with datetime settings but we had weirder issues

@paulirish
Copy link
Member

@brunoxd13 your GMT configuration was in manual mode? this is on windows?

@brunoxd13
Copy link
Author

@paulirish My configurations were in manual mode, I was using Ubuntu Linux

@brunoxd13 brunoxd13 reopened this Sep 18, 2018
@wardpeet
Copy link
Collaborator

i'll spin up an ubuntu vm and try it out

@wardpeet
Copy link
Collaborator

@brunoxd13 how do you set it to manual mode?
image

are you editting /etc/timezone yourself?

@brunoxd13
Copy link
Author

@wardpeet I edited through the interface, I did not use the file at any time.
Change the timezone and try.

@wardpeet
Copy link
Collaborator

I did and no error.

Could you maybe step me through

  1. set timezone to.. ?
  2. open chrome on a page
  3. run lighthouse through the audit panel
  4. lighthouse report has errors about timezone?

@brunoxd13
Copy link
Author

@wardpeet I do not remember very well the configuration of my operating system, however I remember that when you use some website that used the time like WhatsApp, the time was changed.

@brendankenny
Copy link
Member

closing in favor of #6691 (see #6691 (comment))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants