Hello,
Is there anyone attending the Prague hackathon that would be
interested in a session about Huggle developement, how to setup a
development environment and how to participate in development of core,
extensions or scripts?
Thank you
Hi,
New Huggle is out, it's mostly a bugfix release, there were fixes in
logic behind check whether user was recently warned by someone else,
which should finally work properly. The page protection request form
was broken and there were some glitches related to empty edit
summaries, that is still not fully explained, but this version will be
enforcing default revert summaries should configuration contain empty
ones.
Other than that there are some improvements to JS subsystem,
localization updates and so on.
If you find any issues please use phabricator to report these.
P.S. few minutes after release of 3.4.7 I found a major bug in update
last time logic so a quick bugfix was released as well... This is
result of poor beta testing.
Hi all,
Long time no release, and we just got 2 consecutive :) I finally
managed to release Huggle 3.4.5 after so long time and right as I was
testing it on my Windows machine I found a critical bug, so 3.4.6
followed in few minutes.
This e-mail will cover changes from 3.4.4 until 3.4.6
* Version for MacOS is now shipped with brand new Qt 5.12 which I
believe somewhat fixed that terrible multi-keystroke bug. I wanted to
use this on Windows as well, but 5.12 supports only VS 2017 and
internal layout of new VS has changed so I have no idea how to get it
to work with CMake - I would need to read very long documentation to
figure this out and it would probably change in the future anyway so
let's stick with trusted 5.10 for now.
* There was a huge addition in JS scripting - many more things can be
done via scripting now, check out
https://www.mediawiki.org/wiki/Huggle/JS everything there should work
with 3.4.6
* New editing form - you can edit wikipages right in Huggle. There are
bugs though, so consider this an experimental feature (some special
UTF-8 symbols may be removed by this form)
* Loads of bug fixes, minor as well as some major bug fixes
If you find any new bugs, please use phabricator to report them. Thank you
<tl;dr>: Read https://www.mediawiki.org/wiki/Google_Code-in/Mentors and
add your name to the mentors table and start tagging #GCI-2018 tasks.
We'll need MANY mentors and MANY tasks, otherwise we cannot make it.
Google Code-in is an annual contest for 13-17 year old students. It
will take place from Oct23 to Dec13. It's not only about coding:
we also need tasks about design, docs, outreach/research, QA.
Last year, 300 students worked on 760 tasks supported by 51 mentors.
For some achievements from last round, see
https://blog.wikimedia.org/2018/03/20/wikimedia-google-code-in-2017/
While we wait whether Wikimedia will get accepted:
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has some smaller design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?
Note that "beginner tasks" (e.g. "Set up Vagrant") and generic
tasks are very welcome (like "Choose and fix 2 PHP7 issues from
the list in https://phabricator.wikimedia.org/T120336" style).
We also have more than 400 unassigned open #easy tasks listed:
https://phabricator.wikimedia.org/maniphest/query/HCyOonSbFn.z/#R
Can you mentor some of those tasks in your area?
Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Read
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
, ask if you have any questions, and add your name to
https://www.mediawiki.org/wiki/Google_Code-in/2018#List_of_Wikimedia_mentors
(If you have mentored before and have a good overview of our
infrastructure: We also need more organization admins! See
https://www.mediawiki.org/wiki/Google_Code-in/Admins )
Thanks (as we cannot run this without your help),
andre
--
Andre Klapper | ak-47(a)gmx.net
https://blogs.gnome.org/aklapper/
Hi all,
tl;dr
On Monday August 6 we are making EventStreams multi-DC, and this should be
transparent to users.
Due to a recent outage
<https://wikitech.wikimedia.org/wiki/Incident_documentation/20180711-kafka-e…>
of the our main eqiad Kafka cluster, we want to make the EventStreams
service support multiple datacenters for better high availability. To do
so, we need to hide the Kafka cluster message offsets from the
SSE/EventSource clients. On Monday August 6th, we will deploy a change to
EventStreams that will make it use message timestamps instead of message
offsets in the SSE/EventSource id field that is returned for every received
message. This will allow EventStreams to be backed by any Kafka cluster,
with auto-resuming during reconnect based on timestamp instead of Kafka
cluster based logical offsets.
This deployment should be transparent to clients. SSE/EventSource clients
will reconnect automatically and begin to use timestamps instead of offsets
in the Last-Event-ID.
You can read more about this work here:
https://phabricator.wikimedia.org/T199433
- Andrew Otto, Systems Engineer, WMF
Hi,
I updated the virtual system we offer for download for people who want
to do some patches to Huggle, but don't want to spend time settings up
a full featured C++/Qt development environment capable of compiling
Huggle.
The link is here: https://petr.insw.cz/huggle/huggle.ova
You need virtual box to import it. It's a stripped down Ubuntu 18 LTS,
with several packages removed (games, video player, etc) that has
preinstalled all packages needed, with Huggle source codes downloaded
and preconfigured in Qt Creator, so in order to compile Huggle from
latest code you need to just import this VM and launch it.
I updated the old image, so please test this one and let me know if
there is any issue before I push it to wikimedia cloud.
Hi,
New Huggle is out, this version mostly fix stuff (many small annoying
issues), here are more notable things:
* High DPI support - if you have high DPI screen everything should
scale properly and should no longer look pixelated
* Warning template time-based rate limit - by default Huggle will not
send another warning levels to same user too fast after each other, so
that target user has time to read the warning. So if there are 3 edits
made by user and all 3 reverted, Huggle will only send 1 warning.
* RC provider fallback bug resolved
Alright, we are now ready to do this. New date: June 14 2018, around
14:00 UTC.
On Tue, Jun 5, 2018 at 9:31 AM, Andrew Otto <otto(a)wikimedia.org> wrote:
> Hi,
>
> We need to delay this switchover. We’ve made some changes to the plan
> that require a bit more prep work. Follow https://phabricator.
> wikimedia.org/T185225 for more details.
>
> I’ll reply with another announcement email when we set a new date.
>
> - Andrew Otto
> Senior Systems Engineer, WMF
>
>
>
> On Tue, May 15, 2018 at 11:43 AM, Andrew Otto <otto(a)wikimedia.org> wrote:
>
>> Hi all!
>>
>> *If you are not an active user of the EventStreams service, you can
>> ignore this email.*
>>
>> We’re in the process of upgrading
>> <https://phabricator.wikimedia.org/T152015> the backend infrastructure
>> that powers the EventStreams service. When we switch EventStreams to
>> the new infrastructure <https://phabricator.wikimedia.org/T185225>, the
>> ‘offsets’ AKA Last-Event-IDs will change.
>>
>> Connected EventStreams SSE clients will reconnect and not be able to
>> automatically consume from the exact position in the stream where they left
>> off. Instead, reconnecting clients will begin consuming from the latest
>> messages in the stream. This means that connected clients will likely miss
>> any messages that occurred during the reconnect period. Hopefully this
>> will be a very small number of messages, as your SSE client should
>> reconnect quickly.
>>
>> This switch is scheduled to happen on June 5 2018, at around 17:30 UTC.
>>
>> Let us know if you have any questions.
>>
>> Thanks!
>> - Andrew Otto
>> Senior Systems Engineer, WMF
>>
>>
>>
>>
>>
>>
>>
>>
>
Hi all!
*If you are not an active user of the EventStreams service, you can ignore
this email.*
We’re in the process of upgrading
<https://phabricator.wikimedia.org/T152015> the backend infrastructure that
powers the EventStreams service. When we switch EventStreams to the new
infrastructure <https://phabricator.wikimedia.org/T185225>, the ‘offsets’
AKA Last-Event-IDs will change.
Connected EventStreams SSE clients will reconnect and not be able to
automatically consume from the exact position in the stream where they left
off. Instead, reconnecting clients will begin consuming from the latest
messages in the stream. This means that connected clients will likely miss
any messages that occurred during the reconnect period. Hopefully this
will be a very small number of messages, as your SSE client should
reconnect quickly.
This switch is scheduled to happen on June 5 2018, at around 17:30 UTC.
Let us know if you have any questions.
Thanks!
- Andrew Otto
Senior Systems Engineer, WMF
Hi,
So a day after release of 3.4.0 I am releasing 3.4.1, due to couple of
major crash / logic bug findings in 3.4.0 (yes - that's the reason why
I would love to have some beta testers involved more, but to be honest
I fully expected this, 3.4.0 was too major change, there had to be
something wrong that would be discovered once fully rolled out).
So yes, I am now building the packages for all OSes, if you already
have 3.4.0, please update to 3.4.1 ASAP when available, if you have
older Huggle, just wait for 3.4.1 ;)
Thanks