Page MenuHomePhabricator

[Bingle] Comment re-posting is funky (strips delimited hyperlinks and newlines)
Closed, ResolvedPublic

Description

https://mingle.corp.wikimedia.org/projects/analytics/cards/1286

Input:


https://meta.wikimedia.org/wiki/Project_portals

We have project portals such as https://www.wikipedia.org and
https://www.wiktionary.org. It'd be nice to get the raw data of number of
visitors on an hourly basis to the various project (www) portals.

I believe the Wikimedia Analytics team is continuing to look for discrete

projects to work on. Toby: thoughts on this being a 2014Q1 analytics project?

Output (from Mingle):


https://meta.wikimedia.org/wiki/Project_portals We have project portals such as and . It'd be nice to get the raw data of number of visitors on an hourly basis to the various project (www) portals. I believe the Wikimedia Analytics team is continuing to look for discrete projects to work on. Toby: thoughts on this being a 2014Q1 analytics project?

Full bug report at https://bugzilla.wikimedia.org/57828

Looks like hyperlinks inside < and > are eaten, as are line breaks? Filing this under Wikimedia --> Bugzilla, though there's probably a better place.


Version: wmf-deployment
Severity: minor
See Also:
https://github.com/awjrichards/bingle/issues/10
https://bugzilla.wikimedia.org/show_bug.cgi?id=60175

Details

Reference
bz57830

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 22 2014, 2:36 AM
bzimport set Reference to bz57830.
bzimport added a subscriber: Unknown Object (MLST).

(In reply to comment #1)

Should be reported at https://github.com/awjrichards/bingle/issues (wrong
place here) and as written it's covered in
https://github.com/awjrichards/bingle/issues/10

It's directly interacting with Wikimedia's Bugzilla installation. Perhaps it should be marked with "upstream", though.

No sense in having two tickets open if the one in GitHub will automatically also fix the one in this bugtracker...

(In reply to comment #3)

No sense in having two tickets open if the one in GitHub will automatically
also fix the one in this bugtracker...

Perhaps you're unfamiliar with the "upstream" keyword?

Maybe I introduced the keyword myself? There is no " upstream software vendor"

(In reply to comment #5)

Maybe I introduced the keyword myself? There is no "upstream software
vendor"

I'm not sure I'd agree with that. This seems fairly "upstream" to me.

Bugzilla is Wikimedia's bug tracker and this particular script directly interacts with Wikimedia's Bugzilla installation. While I can understand and appreciate that this tool has its own issue tracker on GitHub, allowing Wikimedians to receive e-mail status updates about the progress of this issue via the standard bug tracker rather than requiring Wikimedians to register at a completely separate site is important and within scope, in my opinion.

See https://github.com/awjrichards/bingle/issues/11 and https://github.com/awjrichards/bingle/issues/10 This has been a thorn in our side for a while. Hopefully I'll be able to address this soon, unless someone beats me to it.

The part of this issue concerning line breaks is now resolved (see https://github.com/awjrichards/bingle/issues/10), however it's up to the individual teams who use Mingle to pull the latest. This issue will still be present in those projects until they update.

Ok, now both issues identified in this but report are now resolved in Bingle master (see https://github.com/awjrichards/bingle/issues/11). Again, you may still see issues with teams using outdated Bingle code

  • Bug 60175 has been marked as a duplicate of this bug. ***