Re: MXR permanently offline, please transition to DXR

On 20/07/2016 22:47, Andreas Tolfsen wrote: > Erik Rose writes: > >> > Simple question: How often is DXR refreshed from, say, >> > mozilla-central. >> >> Every 6 hours. However, if it doesn't build successfully, it doesn't >> update (since DXR uses information exfiltrated from

Re: MXR permanently offline, please transition to DXR

> Is this also the case for non-C++ code in the tree? The non-C++ code in a C++ project updates atomically with the C++ code in order to show a coherent view (and search DB) of the project. Projects that have no build step, like webtools, obviously don't run into such build issues.

Re: MXR permanently offline, please transition to DXR

Erik Rose writes: > > Simple question: How often is DXR refreshed from, say, > > mozilla-central. > > Every 6 hours. However, if it doesn't build successfully, it doesn't > update (since DXR uses information exfiltrated from the compiler to > give more accurate search results

Re: MXR permanently offline, please transition to DXR

> Simple question: How often is DXR refreshed from, say, mozilla-central. Every 6 hours. However, if it doesn't build successfully, it doesn't update (since DXR uses information exfiltrated from the compiler to give more accurate search results than MXR). That's what's happening now:

Re: MXR permanently offline, please transition to DXR

Sorry for joining this thread after 77 previous posts, which, admittedly, I haven't all read. Also excuse me if I'm asking something that has been asked/answered before. I tried looking for keywords in the messages (update, index, refresh). Simple question: How often is DXR refreshed from,

Re: MXR permanently offline, please transition to DXR

> All I need now is an open search engine for c-c to plug into Firefox search > box. ;) There's actually a bug open about this already, with some hints on how to get started: https://bugzilla.mozilla.org/show_bug.cgi?id=813521 ___ dev-platform mailing

Re: MXR permanently offline, please transition to DXR

On Monday, July 11, 2016 at 6:45:29 AM UTC-7, Matthew N. wrote: > On Fri, Jul 8, 2016 at 12:27 PM, Lawrence Mandel > wrote: > > > We do in the case of 3rd party software referencing files from MXR (and > > I'm told there is a lot of this). > > > > ​That's an existing

Re: MXR permanently offline, please transition to DXR

On Fri, Jul 8, 2016 at 12:27 PM, Lawrence Mandel wrote: > We do in the case of 3rd party software referencing files from MXR (and > I'm told there is a lot of this). > ​That's an existing problem which is orthogonal to the MXR decommissioning so that doesn't need to be

Re: MXR permanently offline, please transition to DXR

That will be really useful, thanks! All I need now is an open search engine for c-c to plug into Firefox search box. ;) Axel On 11 Jul 2016 03:09, "Peter Elmers" wrote: > If it helps anyone, I happen to know that there exists an addon which > visits all anchor tags on a

Re: MXR permanently offline, please transition to DXR

On Saturday, July 9, 2016 at 12:57:31 PM UTC+10, Boris Zbarsky wrote: > On 7/8/16 7:25 PM, Gerald Squelart wrote: > > The annotate (aka blame) functionality of hg.mozilla.org can point at one > > line > > Yes, I know. What it can't do is highlight some set of lines containing > more than one

Re: MXR permanently offline, please transition to DXR

On 7/8/16 11:37 PM, Eric Rahm wrote: While mxr being retired is unfortunate, at this point would it not make more sense to just file bugs against dxr for features you would like to be added? 1) We're talking about hg.mozilla.org, not dxr. There are existing bug reports on adding line

Re: MXR permanently offline, please transition to DXR

While mxr being retired is unfortunate, at this point would it not make more sense to just file bugs against dxr for features you would like to be added? It's not clear to me after this lengthy discussion if anything actionable has been accomplished. -e On Fri, Jul 8, 2016 at 7:57 PM, Boris

Re: MXR permanently offline, please transition to DXR

On 7/8/16 7:25 PM, Gerald Squelart wrote: The annotate (aka blame) functionality of hg.mozilla.org can point at one line Yes, I know. What it can't do is highlight some set of lines containing more than one line. Think things like: http://mxr.mozilla.org/whatever-file?mark=10-20,17,25#8

Re: MXR permanently offline, please transition to DXR

On Saturday, July 9, 2016 at 7:21:24 AM UTC+10, Boris Zbarsky wrote: > On 7/8/16 4:18 PM, Steve Fink wrote: > > Are either mxr or dxr really the right thing for canonical links to our > > source code? As long as we're updating links, through one means or > > another, temporarily or permanently,

Re: MXR permanently offline, please transition to DXR

On 7/8/16 12:49 PM, Gijs Kruitbosch wrote: In case this is useful for folks: I wrote a webextension that rewrites these links and that obeys the "rev" and "mark" query params from MXR links and rewrites them to the equivalent DXR URL syntax:

Re: MXR permanently offline, please transition to DXR

On 7/8/16 4:18 PM, Steve Fink wrote: Are either mxr or dxr really the right thing for canonical links to our source code? As long as we're updating links, through one means or another, temporarily or permanently, couldn't we come up with a set of urls that would be better in the long term? One

Re: MXR permanently offline, please transition to DXR

I filed bug 1285657 to rewrite MXR links in Bugzilla to DXR. Are there other sites (MDN) that have a lot of links that we should look to rewrite? Lawrence On Fri, Jul 8, 2016 at 3:49 PM, Gijs Kruitbosch wrote: > The problem is that if you're on a bmo page with these

Re: MXR permanently offline, please transition to DXR

On 7/8/16 3:23 PM, Lawrence Mandel wrote: On Fri, Jul 8, 2016 at 11:10 AM, Boris Zbarsky > wrote: Why do we need the interstitial page for direct links to files? What action is expected to be taken by the person who followed that link, other

Re: MXR permanently offline, please transition to DXR

Are either mxr or dxr really the right thing for canonical links to our source code? As long as we're updating links, through one means or another, temporarily or permanently, couldn't we come up with a set of urls that would be better in the long term? One that clearly states the purpose of a

Re: MXR permanently offline, please transition to DXR

The problem is that if you're on a bmo page with these "perma"links, really the ideal case is that they are indeed permalinks and continue to work, especially where they point to specific lines in specific revisions. The interstitial just makes it harder for people to get to that info. A 404

Re: MXR permanently offline, please transition to DXR

We do in the case of 3rd party software referencing files from MXR (and I'm told there is a lot of this). We also can't guarantee that MXR URLs will direct to the right place in DXR. There is likely a balance to be struck here with highly referenced files from 3rd party software getting an

Re: MXR permanently offline, please transition to DXR

Can we skip the interstitial page and make the notice (if any) more unobtrusive somehow? There are tons of mxr links all over the place, and many of them are immutable. We don't gain anything by informing the viewer about their obsolescence instead of showing them the content they want. On Fri,

Re: MXR permanently offline, please transition to DXR

dev-platform was not included on my response below. Looping back in to this fork of the thread. On Fri, Jul 8, 2016 at 10:55 AM, Lawrence Mandel wrote: > Sorry Dao. I have seen some responses. Maybe they were off list. We're > working on details now. I'm going to get

Re: MXR permanently offline, please transition to DXR

On 6/30/16 3:56 PM, Erik Rose wrote: Hi, Kendall. As a pain mitigation strategy for MXR URLs embedded immutably in Bugzilla and in people's Awesomebar histories, can we redirect MXR requests as Dão suggests? This really needs to happen. I've hit broken mxr links from bugzilla comments at

Re: MXR permanently offline, please transition to DXR

On 25/06/2016 13:00, Douglas Turner wrote: > Also, the point that people are making here is that MXR wasn't safe to run > and we are fixing that by decommissioning. You're more than welcome to > deploy this old software but you're going to get shell pop'ed and have a > really bad day. And, trust

Re: URL translation map Re: MXR permanently offline, please transition to DXR

On 2016-07-06 11:08 AM, Tim Guan-tin Chien wrote: I didn't file the bug because I don't know if it make sense to rewrite on the source tree (instead of implementing the rewrite). Feel free to file. Thanks. Bug 1284887 filed, thanks. - mhoye ___

Re: URL translation map Re: MXR permanently offline, please transition to DXR

I didn't file the bug because I don't know if it make sense to rewrite on the source tree (instead of implementing the rewrite). Feel free to file. Thanks. On Wed, Jul 6, 2016 at 9:38 PM, Mike Hoye wrote: > On 2016-07-06 1:46 AM, Tim Guan-tin Chien wrote: > > We really need

Re: URL translation map Re: MXR permanently offline, please transition to DXR

On 2016-07-06 1:46 AM, Tim Guan-tin Chien wrote: We really need to get the vanilla redirect done at least, since, ironically, "mxr.mozilla.org " is even referenced in the code base! https://dxr.mozilla.org/mozilla-central/search?q=mxr.mozilla.org=false Cleaning those

Re: URL translation map Re: MXR permanently offline, please transition to DXR

Tim Guan-tin Chien wrote: A lot of code (including add-ons) out there also rely on MXR URL to fetch, for example, the public suffix list. https://github.com/search?q=https%3A%2F%2Fmxr.mozilla.org%2Fmozilla-central%2Fsource%2Fnetwerk%2Fdns%2Feffective_tld_names.dat=searchresults=Code=%E2%9C%93

Re: MXR permanently offline, please transition to DXR

For now, can we get https://mxr.mozilla.org/ to point to something other than the "Repairs in Progress" hardhat? A redirect to dxr would not be amiss, methinks. On Fri, Jul 1, 2016 at 7:50 AM, Panos Astithas wrote: > It seems like the awesomebar could at least help you by

Re: URL translation map Re: MXR permanently offline, please transition to DXR

On 2016-06-30 9:50 PM, Karl Dubost wrote: Gregory, Le 1 juil. 2016 à 09:33, Gregory Szorc a écrit : I want the site to publish a "URL translation map" for URL patterns so whole URL namespaces can be bulk updated. Interesting idea. Probably something to explain in a wiki

Re: MXR permanently offline, please transition to DXR

It seems like the awesomebar could at least help you by boosting the frecency weight of the new URL compared to the old one, so it can gradually (or even not so gradually) be replaced. We are going to fix this in bug 737836. Panos On Fri, Jul 1, 2016 at 3:58 AM, Justin Dolske

URL translation map Re: MXR permanently offline, please transition to DXR

Gregory, Le 1 juil. 2016 à 09:33, Gregory Szorc a écrit : > I want the site to publish a "URL translation map" > for URL patterns so whole URL namespaces can be bulk updated. Interesting idea. Probably something to explain in a wiki page somewhere on

Re: MXR permanently offline, please transition to DXR

This reminds me of a password manager bug we fixed 9 years ago (379997!), where password manager would "helpfully" delete a saved HTTP login if it got a 403 response upon using it. Unsurprisingly, this was a a terrible idea that caused your saved logins to disappear when a site was glitchy. Seem

Re: MXR permanently offline, please transition to DXR

On Thu, Jun 30, 2016 at 4:55 PM, Robert O'Callahan wrote: > > In theory responses 301 and 308 mean "permanent redirect" so the browser > could do that for those responses. > > In practice you'd need a lot of data to convince yourself that Web > developers haven't screwed

Re: MXR permanently offline, please transition to DXR

On Thu, Jun 30, 2016 at 04:49:26PM -0700, Gregory Szorc wrote: > On Thu, Jun 30, 2016 at 7:20 AM, Dão Gottwald wrote: > > > Can we please automatically redirect from > > https://mxr.mozilla.org/mozilla-central/source/x/y.z to > >

Re: MXR permanently offline, please transition to DXR

On Fri, Jul 1, 2016 at 9:55 AM, Robert O'Callahan wrote: > In theory responses 301 and 308 mean "permanent redirect" so the browser > could do that for those responses. Those would only work for as long as the 3xx is remembered, and it wouldn't work for /x if you have only

Re: MXR permanently offline, please transition to DXR

In theory responses 301 and 308 mean "permanent redirect" so the browser could do that for those responses. In practice you'd need a lot of data to convince yourself that Web developers haven't screwed this up too badly. Maybe 308, being newer, is not compromised... Rob -- lbir ye,ea

Re: MXR permanently offline, please transition to DXR

On Thu, Jun 30, 2016 at 7:20 AM, Dão Gottwald wrote: > Can we please automatically redirect from > https://mxr.mozilla.org/mozilla-central/source/x/y.z to > https://dxr.mozilla.org/mozilla-central/source/x/y.z? My browsing history > is littered with mxr URLs which used to

Re: MXR permanently offline, please transition to DXR

Hi, Kendall. As a pain mitigation strategy for MXR URLs embedded immutably in Bugzilla and in people's Awesomebar histories, can we redirect MXR requests as Dão suggests? Some won't work, but many will, and those people will be less sad. > On Jun 30, 2016, at 10:20 , Dão Gottwald

Re: MXR permanently offline, please transition to DXR

Can we please automatically redirect from https://mxr.mozilla.org/mozilla-central/source/x/y.z to https://dxr.mozilla.org/mozilla-central/source/x/y.z? My browsing history is littered with mxr URLs which used to make it very easy to find a file by typing part of the name. As it stands all those

Re: MXR permanently offline, please transition to DXR

On 06/28/16 01:01, Tanvi Vyas wrote: Is it possible to safely redirect mxr to dxr? This would be most welcome. There are lots of pasted MXR links in Bugzilla comments which now requires tedious editing to follow. /Mats ___ dev-platform mailing

Re: MXR permanently offline, please transition to DXR

Is it possible to safely redirect mxr to dxr? When I use my awesomebar and type "docshell", it pulls up https://mxr.mozilla.org/mozilla-central/source/docshell/base/nsDocShell.cpp. I click enter and end up at the mxr error page. So instead I do a dxr search for docshell and scroll through a

Re: MXR permanently offline, please transition to DXR

Thanks for pointing this out! We've increased the contrast in https://github.com/mozilla/dxr/commit/a0b7afeb82bc9903d8c80494fb487b93ef280b70. Do feel free to file bugs in the future. Cheers, Erik > On Jun 25, 2016, at 0:45 , Philip Chee wrote: > > MXR uses black text

Re: MXR permanently offline, please transition to DXR

Mike Hoye wrote: > On 2016-06-24 6:20 AM, Philip Chee wrote: >> >> I wonder what is necessary to set up an instance of MXR (for comm-*) on >> our own server (or vps). I would guess PERL, hg, and a Linux VM. > I've got the impression that comm-* has enough rocks to push up the > legacy-stack hill

Re: MXR permanently offline, please transition to DXR

On 25.06.2016 06:45, Philip Chee wrote: DXR only gives me mozilla-central. You can choose different repositories using the Switch Tree drop-down menu on the top right. Or keep a bookmark to start with a specific repository like https://dxr.mozilla.org/comm-central/source/ /Stefan

Re: MXR permanently offline, please transition to DXR

Philip, Can you please file bugs. There is no need to discuss your specific eye strain issues or what DXR should or should not index on dev-platform. Also, the point that people are making here is that MXR wasn't safe to run and we are fixing that by decommissioning. You're more than welcome to

Re: MXR permanently offline, please transition to DXR

On 24/06/2016 22:50, glob wrote: > Philip Chee wrote: >> >> I wonder what is necessary to set up an instance of MXR (for comm-*) on >> our own server (or vps). I would guess PERL, hg, and a Linux VM. > > mxr was shutdown due to some very serious security issues; i strongly > advise against

Re: MXR permanently offline, please transition to DXR

On 2016-06-24 6:20 AM, Philip Chee wrote: I wonder what is necessary to set up an instance of MXR (for comm-*) on our own server (or vps). I would guess PERL, hg, and a Linux VM. I've got the impression that comm-* has enough rocks to push up the legacy-stack hill already. - mhoye

Re: MXR permanently offline, please transition to DXR

Philip Chee wrote: I wonder what is necessary to set up an instance of MXR (for comm-*) on our own server (or vps). I would guess PERL, hg, and a Linux VM. mxr was shutdown due to some very serious security issues; i strongly advise against standing up your own instance unless you first put

Re: MXR permanently offline, please transition to DXR

On 24/06/2016 09:41, Edmund Wong wrote: > Ms2ger wrote: >> On 22/06/16 20:30, Lawrence Mandel wrote: >>> Mozilla Cross-Reference, better known as MXR (https://mxr.mozilla.org), was >>> taken offline on June 13, 2016, to investigate a potential security issue. >>> After careful review of the

Re: MXR permanently offline, please transition to DXR

Ms2ger wrote: > On 22/06/16 20:30, Lawrence Mandel wrote: >> Mozilla Cross-Reference, better known as MXR (https://mxr.mozilla.org), was >> taken offline on June 13, 2016, to investigate a potential security issue. >> After careful review of the codebase, we have decided to accelerate the >>

Re: MXR permanently offline, please transition to DXR

On 6/23/16 5:49 AM, Ms2ger wrote: On 22/06/16 20:30, Lawrence Mandel wrote: Mozilla Cross-Reference, better known as MXR (https://mxr.mozilla.org), was taken offline on June 13, 2016, to investigate a potential security issue. After careful review of the codebase, we have decided to accelerate

Re: MXR permanently offline, please transition to DXR

On 06/23/2016 03:49 PM, Ms2ger wrote: On 22/06/16 20:30, Lawrence Mandel wrote: Mozilla Cross-Reference, better known as MXR (https://mxr.mozilla.org), was taken offline on June 13, 2016, to investigate a potential security issue. After careful review of the codebase, we have decided to

Re: MXR permanently offline, please transition to DXR

On 22/06/16 20:30, Lawrence Mandel wrote: > Mozilla Cross-Reference, better known as MXR (https://mxr.mozilla.org), was > taken offline on June 13, 2016, to investigate a potential security issue. > After careful review of the codebase, we have decided to accelerate the > planned transition from

MXR permanently offline, please transition to DXR

Mozilla Cross-Reference, better known as MXR (https://mxr.mozilla.org), was taken offline on June 13, 2016, to investigate a potential security issue. After careful review of the codebase, we have decided to accelerate the planned transition from MXR to its more modern equivalent, DXR (