question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

fe code setup issue

See original GitHub issue

Describe the bug

Local setup and start single report failed.

To Reproduce Steps to reproduce the behavior:

  1. Setup environment:
node --version              
v14.18.1
  1. Execute command
yarn
yarn run start:single
  1. See error
index.js:19 Uncaught RangeError: Invalid time value
    at DateTimeFormat.formatToParts (<anonymous>)
    at partsTimeZone (index.js:19:1)
    at tzIntlTimeZoneName (index.js:15:1)
    at Object.z (index.js:100:1)
    at index.js:344:1
    at Array.reduce (<anonymous>)
    at format (index.js:337:1)
    at formatInTimeZone (index.js:41:1)
    at formatReportTime (formatters.tsx:20:1)
    at SRTablesListPage (SRTablesListPage.tsx:27:1)
react-dom.development.js:18687 The above error occurred in the <SRTablesListPage> component:

    at SRTablesListPage (http://localhost:3002/static/js/bundle.js:3435:5)
    at component
    at Route (http://localhost:3002/static/js/bundle.js:356378:5)
    at Switch (http://localhost:3002/static/js/bundle.js:356432:5)
    at Router (http://localhost:3002/static/js/bundle.js:356364:69)
    at Suspense
    at AppSingle
    at App
    at EnvironmentProvider (http://localhost:3002/static/js/bundle.js:26937:24)
    at ColorModeProvider (http://localhost:3002/static/js/bundle.js:15589:21)
    at ThemeProvider (http://localhost:3002/static/js/bundle.js:44696:64)
    at ThemeProvider (http://localhost:3002/static/js/bundle.js:32475:27)
    at ChakraProvider (http://localhost:3002/static/js/bundle.js:26228:24)
    at ChakraProvider (http://localhost:3002/static/js/bundle.js:27649:23)

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.
logCapturedError @ react-dom.development.js:18687
react-dom.development.js:26923 Uncaught RangeError: Invalid time value
    at DateTimeFormat.formatToParts (<anonymous>)
    at partsTimeZone (index.js:19:1)
    at tzIntlTimeZoneName (index.js:15:1)
    at Object.z (index.js:100:1)
    at index.js:344:1
    at Array.reduce (<anonymous>)
    at format (index.js:337:1)
    at formatInTimeZone (index.js:41:1)
    at formatReportTime (formatters.tsx:20:1)
    at SRTablesListPage (SRTablesListPage.tsx:27:1)

While in terminal everything looks successful.

Compiled successfully!

You can now view piperider-report in the browser.

  Local:            http://localhost:3002
  On Your Network:  http://192.168.1.159:3002

Note that the development build is not optimized.
To create a production build, use yarn build.

webpack compiled successfully
Files successfully emitted, waiting for typecheck results...
Issues checking in progress...
No issues found.

Expected behavior

Setup run successfully and can serve report locally

Screenshots If applicable, add screenshots to help explain your problem.

image

Desktop (please complete the following information):

  • OS: macOS
  • Python Version 3.7.10
  • Piperider Version 0.8.0-dev

Additional context

I’ve followed README.md in static reports folder to init, generated single and comparison report with some sample datasets.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
chenxuanrongcommented, Sep 1, 2022

Thanks @DaveFlynn and @jonycfu for the prompt reply.

I’m now able to set up locally.

image
0reactions
DaveFlynncommented, Sep 1, 2022

Hi @chenxuanrong,

We have managed to reproduce the issue.

Before running npm run start:single, please run compare-reports with the debug flag:

piperider compare-reports --debug

This creates a file comparisons/latest/comparison_data.json, which isn’t actually required for single report, but when missing causes an error before the server is created.

Thanks for pointing us to this issue. We’ll be updating the readme with the additional info soon.

Please let us know if this resolves the problem.

Dave

Read more comments on GitHub >

github_iconTop Results From Across the Web

LG washer error code FE : Causes, How FIX Problem
An FE error indicates that the tank is full. Among its causes are a failure of the central board, a large amount of...
Read more >
LG Washer Code FE – Troubleshooting Guide
The FE error code and overflowing are likely caused by a failed water inlet valve, a faulty pressure switch, or possibly a clogged...
Read more >
How to fix FE error in LG washing machine
Controls the process of dialing a water level sensor. If for some reason the machine draws too much water, having exceeded all permissible...
Read more >
LG Washer FE Error Code [FIXED] - Cause and Solution
The LG washing machine shows an LG washer FE error code, indicating that the water level has reached too high. A faulty inlet...
Read more >
SOLVED: Error code FE - Fixya
The machine stops about 30 minutes into a longer cycle. Cna finish of by setting quick cycle. Error code FE and a bit...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found