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.

Cannot access webiz through browser and tests are failing

See original GitHub issue

I wanted to test webviz locally, therefore I pulled the latest version and tried to open the web app.

What I did so far:

apt update
apt install git nodejs npm curl
npm install -g npm 
npm install -g n
n latest
npm install node-sass  

cd webviz
npm run bootstrap 
npm run build

If now the tests are performed, we get the following error messages:

Summary of all failing tests
 FAIL  packages/webviz-core/src/players/RandomAccessPlayer.test.js (13.188s)
  ● RandomAccessPlayer › backfills previous messages on seek

    Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.

      450 |   });
      451 |
    > 452 |   it("backfills previous messages on seek", async () => {
          |   ^
      453 |     const provider = new TestProvider();
      454 |     const source = new RandomAccessPlayer({ name: "TestProvider", args: { provider }, children: [] });
      455 |     let callCount = 0;

      at Spec (node_modules/jest-jasmine2/build/jasmine/Spec.js:85:20)
      at Suite.it (packages/webviz-core/src/players/RandomAccessPlayer.test.js:452:3)
      at Object.describe (packages/webviz-core/src/players/RandomAccessPlayer.test.js:133:1)

  ● RandomAccessPlayer › discards backfilled messages if we started playing after the seek

    Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.

      537 |   });
      538 |
    > 539 |   it("discards backfilled messages if we started playing after the seek", async () => {
          |   ^
      540 |     const provider = new TestProvider();
      541 |     const source = new RandomAccessPlayer({ name: "TestProvider", args: { provider }, children: [] });
      542 |     let callCount = 0;

      at Spec (node_modules/jest-jasmine2/build/jasmine/Spec.js:85:20)
      at Suite.it (packages/webviz-core/src/players/RandomAccessPlayer.test.js:539:3)
      at Object.describe (packages/webviz-core/src/players/RandomAccessPlayer.test.js:133:1)

 FAIL  packages/webviz-core/src/util/debouncePromise.test.js
  ● debouncePromise › debounces with resolved and rejected promises

    expect(received).toBeUndefined()

    Received: {}

      32 |     await Promise.resolve();
      33 |     expect(calls).toBe(2);
    > 34 |     expect(debouncedFn.currentPromise).toBeUndefined();
         |                                        ^
      35 |
      36 |     debouncedFn();
      37 |     expect(calls).toBe(3);

      at Object.toBeUndefined (packages/webviz-core/src/util/debouncePromise.test.js:34:40)


Test Suites: 2 failed, 73 passed, 75 total
Tests:       3 failed, 748 passed, 751 total
Snapshots:   0 total
Time:        42.682s

I’ll think the proper way of running the web app is to execute npm run docs or? However, the output of the browser at either localhost:8080 or localhost:8080/try is empty.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
surajhpatilcommented, Nov 26, 2019

Sorry for the late response. I am using chrome Version 77.0.3865.90 (Official Build) (64-bit). I figured this out that one of the plugin installed in my browser was causing this issue somehow (fonts related to that plugin). Currently I have bypassed the waitForFont method so that I can at-least load the webviz.

0reactions
jtbandescommented, Nov 26, 2019

This ticket is pretty old and I’m not sure anything more is needed from us here, so I’m going to close it — feel free to file a new ticket with more information if you still need help.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Possible Issues With Web Testing - SmartBear Support
As a result, the following issues may occur in your tests: When you access the current web browser in your system by using...
Read more >
Synthetic Monitoring Troubleshooting - Datadog Docs
My mobile small or tablet browser test results keep failing. If your website is using responsive techniques, its DOM might differ a lot...
Read more >
Cypress can't access a website from its automated browser ...
We attempted to make an http request to this URL but the request failed without a response. We received this error at the...
Read more >
NV WebIZ
Attempting to login to the network without an assigned user account constitutes fraud and misuse of state property, and is punishable under State...
Read more >
How to Clear Browser Cookies to Resolve “Error 500
Once you have gone through all the steps, re-open your browser and log into ... Browsing History” dialog box will appear, click the...
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