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.

Intermittently missing data for largestassets.summary

See original GitHub issue

Since switching to 5.4.1 we’ve had some (seemingly random) failures on some test-runs relating to largestassets.summary.

The error displayed is the following:

[2017-07-19 08:07:37] ERROR: Error: No data to send to graphite for message:
{
  "uuid": "83a5a939-92e0-4a3a-9d69-cc768b712e4a",
  "type": "largestassets.summary",
  "timestamp": "2017-07-19T08:07:37+00:00",
  "source": "assets",
  "data": {
    "plain": []
  },
  "group": "url.that.was.tested
[20170719-sitespeedio-error-log.txt](https://github.com/sitespeedio/sitespeed.io/files/1158767/20170719-sitespeedio-error-log.txt)

"
}
    at Object.processMessage (/usr/src/app/lib/plugins/graphite/index.js:59:29)
    at queue.process (/usr/src/app/lib/support/queueHandler.js:155:57)
From previous event:
    at queue.process (/usr/src/app/lib/support/queueHandler.js:155:42)
    at drainItem (/usr/src/app/node_modules/concurrent-queue/index.js:92:21)
    at Immediate.drain (/usr/src/app/node_modules/concurrent-queue/index.js:73:84)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)

A full log is attached, too [1]. Just re-running the failed one fixes it in all cases that happened so far (probably because the chance of failure itself is relatively low, we run ~30-50 tests per day).

[1]20170719-sitespeedio-error-log.txt

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:7 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
soulgalorecommented, Jul 21, 2017

Released this today, I’ll close it now but please re-open @julrich if you still see it in the logs after upgrading to 5.4.4.

1reaction
soulgalorecommented, Jul 20, 2017

@beenanner you are right, seems like a bug, I think I’ve missed checking in something in the past, the constructor misses some parameters, let me fix that.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Simple descriptive missing data indicators in longitudinal ...
Simple descriptive missing data indicators in longitudinal studies with attrition, intermittent missing data and a high number of follow-ups.
Read more >
Missing Data | Types, Explanation, & Imputation - Scribbr
Missing data, or missing values, occur when you don't have data stored for certain variables or participants.
Read more >
All About Missing Data Handling
Missing data is an everyday problem that a data professional need to deal with. Though there are many articles, blogs, videos already ...
Read more >
MISSING DATA AND DROPOUT - UCLA CTSI
Missing data arise in longitudinal studies whenever one or more of the sequences of measurements are incomplete, in the sense that some intended ......
Read more >
Roll Call: Follow key votes in Congress - La Crosse Tribune
The usual comments from representatives and senators are missing for ... sometimes handwritten, and reference the low end of the estimated ...
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