Re: [Wikitech-l] realtime notifications disabled in Phabricator

[Bill Pirkle]

We were very happy to see workboards updating as we moved tasks during our
Platform Team Clinic Duty Triage meeting today. In fact, we took a quick
break from triaging tasks to have a moment of celebration! This is more
than just a minor convenience - in these meetings we move a lot of tasks
around as a group. These aren't exactly inexpensive meetings for the
Foundation, as we usually have several engineers and managers
participating. So the efficiency we gain via the automatic update is very
real and impactful, and this change is very much appreciated.

Bill Pirkle
Software Engineer
www.wikimediafoundation.org


On Tue, Aug 11, 2020 at 5:05 PM Daniel Zahn  wrote:

> re: >  "aphlict" service had been disabled on Phabricator because it
> caused stability issues.
>
> I am happy to announce that aphlict, the notification service for
> Phabricator using websockets, is now finally back again.
>
> If you allow it in your Phabricator settings you should get realtime
> pop-up notifications again (or for the first time ever if you are
> newer).
>
> Also when tasks are moved around on workboards you should see that
> again without having to reload the page.
>
> In your Phabricator Settings -> Applications -> Notifications you can
> choose from "Web Only", "Desktop Only, "Web and Desktop" or "No
> Notifications".  Up to you which you like most.
>
> --- snip --- some technical details follow if you care ---
>
> aphlict is now running on a dedicated VM just that is separate from
> the main Phabricator server, called aphlict1001.eqiad.wmnet. It is
> running on Debian buster with nodejs 10.
>
> We are not using Apache with "mod_proxy_wstunnel" any longer which
> caused the original instability and even
> if it was still unstable it would not affect the main Phabricator
> anymore as it did in the past.
>
> Also our caching servers (ATS/Varnish) now speak TLS to an envoy-proxy
> on the dedicated backend which then proxies to the aphlict service
> locally. So traffic is encrypted also behind the caching layer and no
> more httpd is involved.
>
> The flow is now:
>
> user client -> wss://phabricator.wikimedia.org (ATS) ->
> ws://:3120 (Varnish) -> wss://aphlict.discovery.wmnet (Envoy)
> -> (local) nodejs:22280
> and  separately  phab1001 ->  aphlict1001:22281
>
> This resolved https://phabricator.wikimedia.org/T238593
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] WikiContrib 2.0 released!

[Daniel Zahn]

Easy to use, works and looks nice.

The activity list of my own contributions is useful and will probably
replace looking at Phabricator feed for
me for some purposes.

Congrats, Raymond.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] WikiContrib 2.0 released!

[Raymond Olisaemeka]

Hello Wikimedians,

We are proud to announce the release of the second version of the
WikiContrib tool:  .

WikiContrib is an easy-to-use developer metrics tool for visualizing the
technical contributions to Wikimedia projects on Phabricator, Gerrit, and
Github. You can view fellow Wikimedians' contributions or share with them a
link to your contribution activity on WikiContrib.

Most relevant changes in this version include:

   -

   Feature to visualize contributions to Wikimedia repositories on GitHub.
   -

   Unique shareable URL for contributions.
   -

   Caching feature to reduce query latency.
   -

   Fixes to long-standing critical bugs.
   -

   User experience improvements.


I worked on these recent changes as part of my Outreachy internship project
with guidance and support from my mentors Srishti Sethi <
https://phabricator.wikimedia.org/p/srishakatux/>,

Rammanoj Potla ,

and Suchakra Sharma .

Relevant Links:

   -

   Tool: https://wikicontrib.toolforge.org
   -

   Source code: https://github.com/wikimedia/wikicontrib
   -

   Proposal: https://phabricator.wikimedia.org/T249175
   -

   Documentation: https://wikicontrib.readthedocs.io/


We invite you to try the tool, and if you encounter any bugs, it would be
helpful if you could report them on the GitHub repository
. We would also love to hear what
more you would like to see in the tool, how you would want to use it, and
any other ideas you might have on the Tool’s talk page:
https://meta.wikimedia.org/wiki/Talk:WikiContrib.

Thanks,

Raymond Ndibe
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] realtime notifications disabled in Phabricator

[Daniel Zahn]

re: >  "aphlict" service had been disabled on Phabricator because it
caused stability issues.

I am happy to announce that aphlict, the notification service for
Phabricator using websockets, is now finally back again.

If you allow it in your Phabricator settings you should get realtime
pop-up notifications again (or for the first time ever if you are
newer).

Also when tasks are moved around on workboards you should see that
again without having to reload the page.

In your Phabricator Settings -> Applications -> Notifications you can
choose from "Web Only", "Desktop Only, "Web and Desktop" or "No
Notifications".  Up to you which you like most.

--- snip --- some technical details follow if you care ---

aphlict is now running on a dedicated VM just that is separate from
the main Phabricator server, called aphlict1001.eqiad.wmnet. It is
running on Debian buster with nodejs 10.

We are not using Apache with "mod_proxy_wstunnel" any longer which
caused the original instability and even
if it was still unstable it would not affect the main Phabricator
anymore as it did in the past.

Also our caching servers (ATS/Varnish) now speak TLS to an envoy-proxy
on the dedicated backend which then proxies to the aphlict service
locally. So traffic is encrypted also behind the caching layer and no
more httpd is involved.

The flow is now:

user client -> wss://phabricator.wikimedia.org (ATS) ->
ws://:3120 (Varnish) -> wss://aphlict.discovery.wmnet (Envoy)
-> (local) nodejs:22280
and  separately  phab1001 ->  aphlict1001:22281

This resolved https://phabricator.wikimedia.org/T238593

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l