User Details
- User Since
- Dec 19 2020, 10:45 AM (17 w, 5 d)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- Bharatkhatri351 [ Global Accounts ]
Fri, Apr 16
Wed, Apr 14
Tue, Apr 13
Mon, Apr 12
Sun, Apr 4
Sat, Apr 3
Hello @Luensu1959
Thanks for you concern
As far as i know the build of portal
At the time of production build of wikimedia.org all templates compile into a single html file and that file is hosted on server.
As you can see in above screenshot Lìgure language is present in 10,000+ group in localhost it's mean every thing is working fine.
It will be updated soon at time of next production build.
If you have any query remains let me know. :-)
Fri, Apr 2
But I have never assigned this task for me i was working on this normally my fault But No worry You can work on it if you have assigned it:)
Go for it ...
# Run npm update y18n --depth 4 to resolve 2 vulnerabilities ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ High │ Prototype Pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Package │ y18n │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Dependency of │ gulp-svg-sprite [dev] │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Path │ gulp-svg-sprite > svg-sprite > yargs > y18n │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ More info │ https://npmjs.com/advisories/1654 │ └───────────────┴──────────────────────────────────────────────────────────────┘
Thu, Apr 1
hello @Iniquity i just see your proposal. In this proposal you mentioned font sizes are not according to the style guide.
Can you tell me the present scenerio if still these changes are required. I would love to work on this.
Wed, Mar 31
Tue, Mar 30
Mon, Mar 29
Sat, Mar 27
Wed, Mar 24
Mar 24 2021
Mar 21 2021
This task should wait until a separate config.js file has been created as part of T277405.
Mar 15 2021
Hey @Iniquity
It looks fine now...Please check this out
hey,
@Jdrewniak
I have moved "helptask" to help.js..kindly review the changes.
Mar 14 2021
ok good idea...
Hey, @Tsiruot i want to work on this task as i observed. you claimed three of the task @Jdrewniak without submitting the patch for it .....Which i think is not a good practice. every one want to contribute..
Thanks : )
its feel great to solve issues..:)
Mar 13 2021
@Dasgupta002 you can use chat stream for your queries....
I have submit the patch again according to your need...please check it out.
I felt #eaecf0 best matches with theme..
"#eaf3ff75" this color was not going with theme and #eaf3ff is very light for a white background.
but i personally felt this hover effect not looking good on articles link. because it showing underline effect too.
But if you feel comfortable with this patch you can merge this : ) .
Hello @Gopavasanth
as this patch is merged now u can review my patch now...
i have noticed this bug is still exist in videocuttool
I have added border and padding according to your instructions...adding border created a small effect in link automatically....
please check is this effect is good for portal or i have to do some changes in it...
Yes, in my opinion the problem has been fixed! All the same, there is no smoothness, but that's another task. Thank :)
If you want i can try to add smoothness...
what exactly do you want in smoothness if you will create a issue for it
i feel happy to work on it.
Thanks:)
Hello @Iniquity
i have decrease width of link border.
is this width seems fine.
from my observation we can't decrease width more than this because it will change other link's text alignment. (some text will come below of other text).
Mar 12 2021
I gone through this issue deeply...this actually not a browser bug...
this is human typo error.
Because time delay was set 400s which was very much....
I have fixed the issue.
Please check this out
Mar 11 2021
Convert your browser language to persian (from settings of your browser).Then Open wikipedia portal main page then you can observe this issue..
i have mentioned some screenshots of issue above....
@Jdrewniak
thats fine..
hope they will be fixed in future..
┌──────────────────────────────────────────────────────────────────────────────┐
│ Manual Review │
│ Some vulnerabilities require your attention to resolve │
│ │
│ Visit https://go.npm.me/audit-guide for additional guidance │
└──────────────────────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Moderate │ Denial of Service │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ js-yaml │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=3.13.0 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ gulp-cssnano [dev] │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ gulp-cssnano > cssnano > postcss-svgo > svgo > js-yaml │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/788 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Code Injection │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ js-yaml │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=3.13.1 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ gulp-cssnano [dev] │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ gulp-cssnano > cssnano > postcss-svgo > svgo > js-yaml │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/813 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ gulp-svg-sprite [dev] │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ gulp-svg-sprite > svg-sprite > mocha > mkdirp > minimist │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1179 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ yargs-parser │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >=13.1.2 <14.0.0 || >=15.0.1 <16.0.0 || >=18.1.2 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ gulp-svg-sprite [dev] │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ gulp-svg-sprite > svg-sprite > yargs > yargs-parser │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/1500 │
└───────────────┴──────────────────────────────────────────────────────────────┘
This task involves running npm audit --fix to fix 7 of them.
Fixed 7 of them...using npm audit fix...
how can remaining dependicies can be fixed manually?
Mar 9 2021
But I am not sure if we're just talking about the numerals used for displaying articles count because those are the only numerals which are not converted to the local string.
Because fa.wikipedia.org correctly translates all the numerals to Eastern Arabic.
Correct me if I am wrong but currently only main portal has the JavaScript based translation mechanism, then
Mar 3 2021
Mar 2 2021
I have deep dug regarding this bug.
Feb 25 2021
hello @Jdrewniak
I am working on this isssue can you help me out please i am stuck at a point
i have change my browser prefered language and this result as shown
but i am not able to see language changes in my localhost its still shows in english
so how can i observe changes
if i do some change in persian language.
or changes in function to observe it on persian lang.
Feb 24 2021
Hello
I want to work on this issue.
I made a researched about the issue what this issue exactly demands
Can you give me some insights so i can proceed further to solve this issue.
And i also want to know that how can i convert the language of wikipedia portal from english to persian language.
Because at main page https://www.wikipedia.org/ i can only see the option to read articles in persian not to convert the language of the page
and a search box where i can search any article in persian
Feb 23 2021
Hello @Techwizzie Are You still working on this issue???
Feb 22 2021
Feb 20 2021
May be gulp global dependencies is not required.
@Shivas1000 i am still working on this issue.
actually i am new to gulp so i am learning it to solve the issue.
But if you have prior experience with gulp
u can solve this.. :)
Feb 18 2021
hey @Jdrewniak i learned basics of gulp to understand this issue..
Can you tell me is i am thinking right or not
According to this we have to convert all gulp function in npm scripts.
like compilation and minification watch CreateSvgSprites etc.
and totally remove gulp.js from it
@Jdrewniak
As it Mentioned above Readme file is not updated.
so according to the issue i have to remove site-def.json , site-def.js , site-state.json text from readme
so what i have to write in place of this text.
which script and file are doing those function now
which are done by those files earlier.(site-def.json , site-def.js , site-state.json)
Feb 17 2021
@Jdrewniak thankx for your support i will try to use window linux system.
Feb 15 2021
Hi @Bharatkhatri351, I'm sorry you're having trouble with the build pipeline.
The problem you'r encountering looks to be that the following path is incorrect.
E:\portals\dev\wikipedia.org/assets/l10n
The following string /assets/l10n/**/*.json assumes a unix-based development machine, and isn't formatted to work on Windows.I'm going to have to review that code and make sure it uses the Node path.resolve() functions to allow it to work on windows.
I'm sorry for this issue, but I'll review this code on Windows this week and hopefully I'll have this resolved soon.
@Khr2003 Nicely Done...
Appreciable Man :)
Feb 10 2021
@SarthakKundra Actually i was not able to run this project in my pc because of a some path issue. As @Jdrewniak told me he will fix this issue in somedays
(for window users). So when the issue will be fix i will start working on it.
But if This project somehow is running on you pc you can resolve this issue.:)
Feb 9 2021
Feb 8 2021
I am getting this error tried a lot but not able to resolve this.
any idea what is going wrong.????????