@aranhoide thanks.  That invite is still in the authorized state, so
something must have gone wrong with starting up that proxy.  What would be
the best way to troubleshoot?


Cheers,
Ox

-----------------------------------------------------------------------------------------

"I love people who harness themselves, an ox to a heavy cart,
who pull like water buffalo, with massive patience,
who strain in the mud and the muck to move things forward,
who do what has to be done, again and again."

- Marge Piercy



On Thu, Jan 16, 2014 at 6:51 AM, aranhoide <notifications@github.com> wrote:

> In app/partials/modals.html:
>
> > @@ -300,7 +300,7 @@
> >                    <span class="email">{{ friend.email }}</span>
> >                  </span>
> >                  <div ng-class="{'pull-right': true, 'btn-group': true, transparent: state.showAddRmIdx != $index}">
> > -                  <button ng-click="add(friend.email)" class="btn btn-mini btn-success" ng-disabled="pendingFriendUpdate">{{'ADD' | i18n}}</button>
> > +                  <button ng-click="add(friend.email)" class="btn btn-mini btn-success" ng-disabled="pendingFriendUpdate || !friend.freeToFriend">{{'ADD' | i18n}}</button>
>
> That means that the fallback proxy that will serve the new invitee is
> still starting up. When the controller gets the SQS message announcing that
> a proxy is up, it 'thaws' and processes all authorized invites assigned to
> that proxy.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/getlantern/lantern-ui/pull/71/files#r8930161>
> .
>