Patrick Hulce

@synergychen cd to a different directory within `/tmp` before running LHCI or edit `node_modules/@lhci/utils/src/saved-reports.js` to whatever directory you'd like. https://github.com/GoogleChrome/lighthouse-ci/blob/932a5fe98412df705e98e0866600c176db790212/packages/utils/src/saved-reports.js#L10

Hello again @jflayhart thanks for filing :) In general, this won't work. From the docs... > NOTE: If you run a matrix of environments in your tests, make sure you...

Thanks for filing @rdelgatte! Proxy support is not great in node and most node http libraries. We would need to thread this through ourselves (see https://github.com/node-fetch/node-fetch/issues/195) to support this. As...

Thanks for filing @Kudja! I'm not able to reproduce this with just the steps provided though.  (Note that the diff is small relative to CLS thresholds so it is...

> It doesn't look like a good idea to hide such changes Not for performance metrics, I agree. We'll add an exception here for performance metrics 👍 Good first issue...

great @sohamsshah! in the section that https://github.com/GoogleChrome/lighthouse-ci/issues/689#issuecomment-923016077 highlighted, make an exception for any audits that are metrics (either a hard-coded list of IDs or checking membership in a group called...

Thanks for filing @ianjmacintosh! What if LHCI just directly exposed the ability to have a javascript function customize the description? Several people have had several conflicting opinions over the years...

Feel free to go for it @ianjmacintosh! I imagine the trickiest parts are going to be just documenting it accurately since it will require a javascript config in order to...

Thanks for filing @xerosanyam! This error means that the server isn't responding to the connection. If it's a localhost or dev server URL, that usually just means the server crashed...

Thanks for filing @niieani! > Passing in --settings to CLI is broken. > --settings flag is supposed to work as designed :) This is not how it was designed :)...