Page MenuHomePhabricator

Users reporting issues with reviews.facebook.net
Closed, WontfixPublic

Description

Harish_: hi, i am trying to update a patch for https://reviews.facebook.net/D13443; run 'arc diff origin/trunk'; I get a 'ERR-CONDUIT-CORE: You can not access the user inside the implementation of a Conduit method...' error

I wasn't able to reproduce this issue or figure out what was going on, and it seems like only FB has access to the host. The FB'ers in Phabricator said you might be the best point of contact, @scottmac.

In the small scale: if you can lift a stack trace off the server, I might be able to figure out what's going on here and fix it.

In the larger scale, there's some context from last time in T1206, but this install:

  1. Uses weird custom JIRA integration which is now two phases of infrastructure out of date (T1206 had a modernization, modern Phabricator hooks directly to JIRA). I believe the modernization never happened, although I thought the old stuff would have broken without it, so maybe this got resolved in some other way.
  2. Uses a weird policy hack -- differential.anonymous-access -- which had never worked properly and which is now obsolete with T603.
  3. Although it seems to have been getting updated more regularly since T1206, we still have a weird three-party dance when support stuff comes up.

It would be nice to clean these issues up at some point, since they're likely to break down the road if not addressed. In particular, we plan to remove differential.anonymous-access.

Event Timeline

epriestley assigned this task to scottmac.
epriestley raised the priority of this task from to Needs Triage.
epriestley updated the task description. (Show Details)
epriestley added subscribers: epriestley, jamesgpearce, Unknown Object (MLST), ashutoshc.

I'm going to close this since there's nothing more we can do on the Phabricator side and it seems like Facebook isn't responding.

@ashutoshc, if you're interested in sticking with Phabricator for code review I'd maybe consider moving to an install you control, since Facebook doesn't seem to have much bandwidth to maintain the reviews.facebook.net install. We're happy to help support such an install, but there's nothing we can do when no one has access to the logs or machine and we can't reproduce issues (and even if we did fix things, it wouldn't help you if no one can update the install).

Sorry for the late response. I'll upgrade this again later tonight and look for a stack trace.

On 17 Oct 2013, at 17:47, "epriestley (Evan Priestley)" <noreply@phabricator.com> wrote:

epriestley created this task.
epriestley assigned this task to scottmac.
epriestley added subscribers: epriestley, jamesgpearce, FacebookPOC, ashutoshc.

TASK DESCRIPTION

Harish_: hi, i am trying to update a patch for https://reviews.facebook.net/D13443; run 'arc diff origin/trunk'; I get a 'ERR-CONDUIT-CORE: You can not access the user inside the implementation of a Conduit method...' error

I wasn't able to reproduce this issue or figure out what was going on, and it seems like only FB has access to the host. The FB'ers in Phabricator said you might be the best point of contact, @scottmac.

In the small scale: if you can lift a stack trace off the server, I might be able to figure out what's going on here and fix it.

In the larger scale, there's some context from last time in T1206, but this install:

  1. Uses weird custom JIRA integration which is now two phases of infrastructure out of date (T1206 had a modernization, modern Phabricator hooks directly to JIRA). I believe the modernization never happened, although I thought the old stuff would have broken without it, so maybe this got resolved in some other way.
  2. Uses a weird policy hack -- differential.anonymous-access -- which had never worked properly and which is now obsolete with T603.
  3. Although it seems to have been getting updated more regularly since T1206, we still have a weird three-party dance when support stuff comes up.

    It would be nice to clean these issues up at some point, since they're likely to break down the road if not addressed. In particular, we plan to remove differential.anonymous-access.

TASK DETAIL
https://secure.phabricator.com/T3982

To: scottmac, epriestley
Cc: epriestley, jamesgpearce, FacebookPOC, ashutoshc

I upgraded the instance on Wednesday and got access to the error logs but couldn't see anything