Hello all,
I am trying to run a pywikibot based bot on toolforge server.
i logged into tool forge.
Cloned the pywikibot.
created the user-config.py and user-password.py with below content.
cat user-config.py
mylang = 'pa'
family = 'wikisource'
usernames['wikisource']['pa'] = 'WD-WS Integration Bot'
usernames['wikidata']['wikidata'] = 'WD-WS Integration Bot'
password_file = "user-password.py"
cat user-password.py
('WD-WS Integration Bot', BotPassword('wd-ws-integration-bot', 'PASSWORD HERE'))
Created bot account at pa.wikisource.orghttps://pa.wikisource.org/wiki/User:WD-WS_Integration_Bot
Can login to the pa.wikisource.org with the same user name and credentials.
But, cant login using the command line using pwb.py.
Getting the below error.
tools.wdwsbot@tools-sgebastion-07:~/pywikibot-core$ python3
/data/project/shared/pywikibot/stable/pwb.py login
WARNING: No user is logged in on site wikisource:pa
Logging in to wikisource:pa as WD-WS Integration Bot@wd-ws-integration-bot
Traceback (most recent call last):
File "/mnt/nfs/labstore-secondary-tools-project/pywikibot/public_html/core_stable/pywikibot/data/api.py",
line 2931, in login_to_site
response['messagecode'] == 'login-throttled'
KeyError: 'messagecode'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/data/project/shared/pywikibot/stable/pwb.py", line 365, in <module>
if not main():
File "/data/project/shared/pywikibot/stable/pwb.py", line 360, in main
file_package)
File "/data/project/shared/pywikibot/stable/pwb.py", line 74, in
run_python_file
main_mod.__dict__)
File "/data/project/shared/pywikibot/stable/scripts/login.py", line
151, in <module>
main()
File "/data/project/shared/pywikibot/stable/scripts/login.py", line
139, in main
site.login(autocreate=autocreate)
File "/mnt/nfs/labstore-secondary-tools-project/pywikibot/public_html/core_stable/pywikibot/site/_apisite.py",
line 388, in login
if login_manager.login(retry=True, autocreate=autocreate):
File "/mnt/nfs/labstore-secondary-tools-project/pywikibot/public_html/core_stable/pywikibot/login.py",
line 307, in login
self.login_to_site()
File "/mnt/nfs/labstore-secondary-tools-project/pywikibot/public_html/core_stable/pywikibot/data/api.py",
line 2939, in login_to_site
'handled:\n{}'.format(response))
pywikibot.exceptions.CaptchaError: Captcha encountered which cannot be handled:
{'result': 'Failed', 'reason': 'Incorrect username or password
entered. Please try again.'}
CRITICAL: Exiting due to uncaught exception <class
'pywikibot.exceptions.CaptchaError'>
Need help to solve this.
Thanks.
--
Regards,
T.Shrinivasan
My Life with GNU/Linux : http://goinggnu.wordpress.com
Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com
Get Free Tamil Ebooks for Android, iOS, Kindle, Computer :
http://FreeTamilEbooks.com
Hello all,
The 2021 Board of Trustees election[1] is coming soon. Candidates from the
community are needed to fill the available seats.
The Wikimedia Foundation Board of Trustees oversees the Wikimedia
Foundation's operations. Community trustees and appointed trustees make up
the Board of Trustees. Each trustee serves a three-year term. The Wikimedia
community has the opportunity to vote for community trustees.
Wikimedia contributors will vote to fill four seats on the Board in 2021.
This is an opportunity to improve the Board's representation, diversity,
and expertise as a team.
For potential candidates:
- *Traits:* Wikimedia is a global movement and seeks candidates from the
broader community. Candidates should think about what experiences and
perspectives they will bring to the Board. Ideal candidates align with the
Wikimedia mission and are thoughtful, respectful, and community-oriented.
The Board would like to find perspectives and voices that are
under-represented and essential for our movement. They should bring what
Wikimedia needs from a new Trustee.
- *Commitment: *Trustees serve a three-year term and can serve up to
three consecutive terms. The time commitment is about 150 hours per year,
excluding travel. This time is not evenly spread throughout the year. The
time is concentrated around meetings. The expectation is that Trustees
serve on at least one of the Board’s committees.
- *Requirements*[2]: English is the language of business for the Board.
Candidates need a basic understanding of English, but support and training
are part of onboarding. Candidate applications will be translated into
several languages to reach a broad audience of voters.
- *Apply*[3]: Candidates from all projects and communities who meet the
needs of Wikimedia Trustee are welcome. If you know someone who could be a
good trustee, encourage them to run for election. Candidates can find
information and submit their nomination on the Apply to be a Candidate page.
- *Resources*[4]: A toolkit has been developed for community members who
are considering submitting their candidacy for the Wikimedia Foundation
Board of Trustees, and who want to better understand what to expect and how
to prepare for the role.
Thank you for your support,
The Wikimedia Foundation Board of Trustees
[1]
https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation_ele…
[2]
https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation_ele…
[3]
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2021/Apply_t…
[4]
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/Candidate_Re…
--
Krishna Chaitanya Velaga (he/him)
Board Governance Facilitator, Wikimedia Foundation
Hallo.
What are the parts of a template?
When templates started in 2003 or 04, they were just simple pages, whose
content you could add ("transclude") to multiple other pages.
Over time they acquired more features: noinclude, includeonly, onlyinclude,
parser functions, documentation pages, TemplateData, Scribunto,
TemplateStyles, and more.
If we now take a look at the parts from which a template is built, what
will we identify? I'm not talking just about the technical parts, i.e. how
the parser sees it, but also about the functional parts—how the template
maintainers and users perceive it.
Here's what I can think of:
* The body: The content that is actually inserted into other pages. This
can be further divided into text, formatting, images, and logic using
parser functions and invoked modules, but for the sake of parsing it's
probably one blob of wikitext, but do correct me if I'm wrong. Sometimes,
but not always, appears in <includeonly> or <onlyinclude>.
* The documentation: As a separate page (Template:Name/doc), as some
content in <noinclude>, or a mix of both.
* The categories: Self-explanatory. Usually in <noinclude>.
* TemplateData: Usually in a <templatedata> tag on the template page
itself, or on the /doc page.
* TemplateStyles: On a separate page with a different content model, and
linked using <templatestyles> tag. One TemplateStyles page can serve
several other pages, so it's autonomous and modular.
* Testing pages: A few complex templates also have testing or sandbox
pages. I'm familiar with some examples, such as
https://en.wikipedia.org/wiki/Template:Infobox_philosopher/sandbox , but
I'm not an expert on how consistent it is. It's probably not right to call
it a "part" of a template _technically_, but it's closely related to it, so
it can be considered a _functional_ part.
A couple of comments:
1. I mostly deal with Wikimedia use cases. Comments from other wikis are
welcome, too—SMW wikis, your enterprise wiki, Fandom, other farms, etc.
2. I intentionally don't include in this list other templates and Scribunto
modules that a template transcludes or invokes. It's very common, but these
are autonomous. (I do include TemplateStyles, which can also serve several
pages, and maybe I should exclude them, too).
So, two questions:
1.Does it make sense generally?
2. Am I missing anything?
Thanks :)
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Hi everyone.
My patch[1] to remove the legacy `Revision` class from core was just
merged, and this may have broken some extensions. Extensions deployed on
WMF wikis had already been updated, but others may no longer work on
MediaWiki 1.37.
All code using Revision objects had been emitting deprecation warnings
since at least 1.35. I've also created a basic guide[2] to help migrate
extensions that were not updated. This includes how to migrate code relying
on hooks that passed Revision objects - all such hooks have been removed.
You can check out the phabricator task[3] for more info on what
specifically was removed.
Special thanks to the Platform Engineering team, and specifically Petr
Pchelko, for helping out and reviewing a whole bunch of patches.
Thanks,
-DannyS712
[1] https://gerrit.wikimedia.org/r/c/mediawiki/core/+/684071
[2] https://www.mediawiki.org/wiki/Manual:Revision.php/Migration
[3] https://phabricator.wikimedia.org/T247143
This is a summary of this week's deployment of the 1.37.0-wmf.9 branch
of MediaWiki and its extensions (also known as "the train"). The primary
person in charge this week is Jeena Huneidi, with Mukunda Modell as
backup, both from the Wikimedia Foundation Release Engineering team.
The summary/blocker task for this week is
https://phabricator.wikimedia.org/T281150
The new version is running on all sites: https://versions.toolforge.org/
Please note that the next train will be 1.37.0-wmf.11, since the week of
June 14th is taken up by the WMF's annual All Hands.
== Blockers ==
There were a total of four blockers for this train:
* Regression: Echo new talk page message banner has lost its orange
background
** https://phabricator.wikimedia.org/T284496
* regression: Reply tool padding and height broken
** https://phabricator.wikimedia.org/T284567
* TypeError: Argument 1 passed to LanguageConverter::__construct() must
be an instance of Language, instance of StubUserLang given, called in
/srv/mediawiki/php-1.37.0-wmf.9/includes/language/LanguageConverterFactory.php
on line 132
** https://phabricator.wikimedia.org/T284685
* Code editor failing to load completely on English Wiktionary
** https://phabricator.wikimedia.org/T284716
== Deprecation notices ==
Release Engineering has recently adopted the practice of filing
deprecation notices in production as blockers for the following train.
For 1.37.0-wmf.11, we've filed:
* PHP Deprecated: Passing extra fields (quality) to
LocalFile::loadFromRow was deprecated in MediaWiki 1.37. Property
assignment will be removed in a later version. [Called from
OldLocalFile::loadFromRow]
** https://phabricator.wikimedia.org/T284777
== 🚂💗 ==
As usual, lots of people helped find, triage, and solve problems with
this train. Thanks to all involved (listed by Phabricator username):
* DannyS712
* matmarex
* Zabe
* Ladsgroup
* ovasileva
* Jdlrobson
* Edtadros
* Esanders
* ppelberg
* Erutuon
* Xiplus
* Urbanecm
...and anyone else we've missed. Without your help we wouldn't be able
to deploy the train.
Thanks!
-- Your train conductor collective
Hi All
There will be no deployments to Wikimedia production the week of 2021-06-14
(2021-06-14–2021-06-18) for Wikimedia Foundation's annual All Hands.
There is a long-term calendar of upcoming known deployment disruptions
available on Wikitech:
https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar
Thanks!
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
All,
As Node 10 is EOL, many of our upstream tools have been dropping Node 10
support recently, which is slowing down development and creating work for
teams.
I have thus created the Node 12 CI infrastructure (T284343
<https://phabricator.wikimedia.org/T284343>) based on Debian Bullseye
(thank you, SRE Service Ops!) and have today migrated almost all jobs over
to use them (T284345 <https://phabricator.wikimedia.org/T284345>).
There are a small handful of jobs (for Kartotherian, OOUI, and WikiPEG)
that need further infrastructure work, and have not yet been migrated. I've
submitted a few commits switching repos with .nvmrc files over to the new
version installed in CI.
This should be an uneventful change; I've spot-checked a few dozen repos
and not found any issues. If there are any, please shout on the task or in
#wikimedia-releng on Libera.Chat so I can fix it.
Note: This only applies to the centrally-managed legacy CI jobs. If your
repo is using the modern pipeline, you will need to wait for there to be an
appropriate base image, which is tracked in T284346
<https://phabricator.wikimedia.org/T284346>.
J.
--
*James D. Forrester* (he/him <http://pronoun.is/he> or they/themself
<http://pronoun.is/they/.../themself>)
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello,
The committee has finished selecting new members and the new committee
candidates are (In alphabetical order):
- Amir Sarabadani
- Kunal Mehta
- Martin Urbanec
- MusikAnimal
- Tony Thomas
And auxiliary members will be (Also in alphabetical order):
- Ariel Glenn
- Effie Mouzeli
- Huji
- Jayprakash12345
- Nuria Ruiz
You can read more about the members in the mediawiki.org page
<https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Members/Candidates>
.
The changes compared to last term are:
- Kunal Mehta is joining the main CoC committee
- Ariel Glenn is coming back to auxiliary committee
- Effie Mouzeli is joining auxiliary committee for the first time
- Tonina Zhelyazkova is leaving the committee
- Matanya and Tpt are leaving the auxiliary committee
- I won't run for the chair this year.
This is not the final structure. According to the CoC
<https://www.mediawiki.org/wiki/Code_of_Conduct/Committee#Selection_of_new_m…>,
the current committee publishes the new members and calls for public
feedback for *six weeks* and after that, the current committee might apply
changes to the structure based on public feedback.
Please let the committee know if you have any concern regarding the members
and its structure until *26 May 2021* and after that, the new committee
will be in effect and will serve for a year.
Amir, On behalf of the Code of Conduct committee
Best