Last modified: 2014-02-21 01:04:13 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 T59830, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 57830 - [Bingle] Comment re-posting is funky (strips delimited hyperlinks and newlines)
[Bingle] Comment re-posting is funky (strips delimited hyperlinks and newlines)
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
wmf-deployment
All All
: Lowest minor (vote)
: ---
Assigned To: Nobody - You can work on this!
: upstream
: 60175 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-02 07:24 UTC by MZMcBride
Modified: 2014-02-21 01:04 UTC (History)
6 users (show)

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


Attachments

Description MZMcBride 2013-12-02 07:24:13 UTC
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.
Comment 1 Andre Klapper 2013-12-13 12:20:20 UTC
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
Comment 2 MZMcBride 2013-12-13 13:15:58 UTC
(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.
Comment 3 Andre Klapper 2013-12-13 14:17:11 UTC
No sense in having two tickets open if the one in GitHub will automatically also fix the one in this bugtracker...
Comment 4 MZMcBride 2013-12-14 06:29:53 UTC
(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?
Comment 5 Andre Klapper 2013-12-14 14:19:49 UTC
Maybe I introduced the keyword myself? There is no " upstream software vendor"
Comment 6 MZMcBride 2013-12-14 15:29:23 UTC
(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.
Comment 7 Arthur Richards 2014-02-12 17:37:18 UTC
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.
Comment 8 Arthur Richards 2014-02-21 00:37:40 UTC
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.
Comment 9 Arthur Richards 2014-02-21 01:03:31 UTC
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
Comment 10 Arthur Richards 2014-02-21 01:04:13 UTC
*** Bug 60175 has been marked as a duplicate of this bug. ***

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


Navigation
Links