Last modified: 2013-07-25 07:06:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T52065, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50065 - GettingStartedNavbar logs events with null action
GettingStartedNavbar logs events with null action
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
GettingStarted (Other open bugs)
unspecified
All All
: High normal (vote)
: ---
Assigned To: Matthew Flaschen
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-23 18:48 UTC by Ori Livneh
Modified: 2013-07-25 07:06 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ori Livneh 2013-06-23 18:48:51 UTC
in ext.gettingstarted.taskToolbar.js, lines 127-129, we call:

>    var schemaAction = logging.getPageSchemaAction();
>
>    logging.logImpression( fullTask, schemaAction );

But 'getPageSchemaAction' can return null, and logImpression does not check for that, and the schema does not allow nulls.
Comment 1 Steven Walling 2013-06-24 07:34:21 UTC
We looked this up some tonight in the error logs, and it looks like this is less than 1% of events for GettingStartedNavBar, and that most of the errors are coming from the returnto funnel. We should confirm what is causing this if we can, but so far it doesn't look this would have had a big negative impact on the reliability of test results.
Comment 2 Gerrit Notification Bot 2013-06-24 21:41:34 UTC
Related URL: https://gerrit.wikimedia.org/r/70327 (Gerrit Change I329f5992900945535fbd5431eb53f13ecddb9e4b)
Comment 3 Matthew Flaschen 2013-06-24 21:43:15 UTC
It's expected actions that are not logged, such as history (there is no page-history-impression).  That patch prevents it from logging if schemaAction is falsy, which should do it.
Comment 4 Matthew Flaschen 2013-06-25 21:15:17 UTC
Merged.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links