can you try on other manipulations as well @Punith.nyk?
i tried mute and it worked fine so :)

for fetching the current wikiText of the video use this api https://en.wikipedia.org/w/api.php?action=parse&page=Pet_door&prop=wikitext&formatversion=2
and as far as wikitext for newly uploaded videos is concerned, we'll have to discuss some stuff on that

Seems to work fine on prod :(
maybe upload a video regarding the same

probably to deal with sockets, and so the patch will be rebased on top of T338308

T331235 parallel task found :(

here's a patch which has similar workings, and shall clear this out
https://gerrit.wikimedia.org/r/c/labs/tools/VideoCutTool/+/890137

hey @Bennylin we have submitted a patch/pr regarding this issue, and it will be merged within a week
Thanks for raising the query :)

hey @Bennylin thanks for raising the query. As the tool is undergoing some changes and development, we will try to fasttrack this query asap

hey @Bennylin thanks for raising the query. As the tool is undergoing some changes and development, we will try to fasttrack this query asap

hey @Bennylin , thanks for raising this query. As currently we are working on this tool, we will come up with a solution to this, and shall resolve this query

The patch https://gerrit.wikimedia.org/r/928998 deals with fixing the architecture when one user deals with multiple videos.

hey @Gopavasanth, we have a resolved issue around the same task here T333403
its still not reflected in production. We will soon push it there

hey @Bennylin we have the existing issue regarding this T337147, thanks for reporting, and we are working on this
Sorry for the inconvenience caused.
If you wish to track the progress, you can check out the gerrit patch against T337147

This task aims to improve the architecture of the tool, and perform stress testing when multiple users try to use it at the same time

Seems like node-fetch doesn't support Common Js modules, so we will be pausing the work here.
Upgrading to NodeJs 18 LTS, brings fetch API inbuilt, and so will be continuing after upgrade to node 18 is success.

hey @Punith.nyk i won't be able to finish this thing up.. if you want you can take this up :)

The patch currently in review fixes this, and catches all the warnings of the Upload API, and send users the corresponding notification

This is now resolved, as we have migrated to Vite, which does not use Webpack behind the scenes :)

Migrated to Vite successfully :)

will be looking into sequelize migrations, and will change the model declarations.

this shall be closed by https://gerrit.wikimedia.org/r/c/labs/tools/VideoCutTool/+/922118/
as we will be using Vite instead of CRA, and so will be moving away from Webpack bundler to Rollup

hey @Gopavasanth , i encountered this before, and have created a phab task and a gerrit patch regarding the same
I'll link it here, for reference
Phab Ticket: T332605
Patch for the same: https://gerrit.wikimedia.org/r/c/labs/tools/VideoCutTool/+/901242

Let's give this a good-first-issue tag for new developers, to start with.
The file you'll be needing is ./src/components/UrlBox.jsx to start with
Hope this helps :)

Will have to add sass compiler to the project dependencies, and will have to write a script for watching all the .scss files, in the DockerFile

One solution to this can be to configure webpack, by running all the scripts seperately.
Another approach can be to shift from CRA to vite, which removes Webpack from the scene entirely.
Will see if this works out Migrate from CRA

Hey @Gopavasanth, i thought irrespective of the fact that the client shows .mp4 extension, the file on the server which we are uploading to the commons should be of .webm format
I mean this is the expected behaviour. I may be wrong. I'll have to check if the file name on uploading has a .mp4 extension to it. If thats the case (as reflected in the client), I'll change the file name to be the updated file name in .webm or .ogv format.

Instead of web audio api, we will be going with the volume attribute of the HTML video tag

One vague solution is to alter the ffmpeg commands for storing the edited video on the server, and use web audio api for the client side to render it on the go.
Will have to look more into these solutions.

hey @Gopavasanth, is this still open? From what i can see from the commons talk, and related patches, we have a licensing category of cc in the field, and have {extracted from} in it as well.
Do we want to show the name of the license fetched from the wiki page? Currently we are showing {{self|cc-by-sa-4.0}} by default, which should work.
If we want more verbose, We can show the full license name, fetching from MediaWiki API: action=query meta=siteinfo param=rightsinfo here.

September 6:
Final results of Google Summer of Code 2017 announced

hey @Gopavasanth. @Soda, i have made the required changes, and will be uploading it to google. If you find something not fitting right, please do leave the feedback for the same :).
Thanks

Here is a parallel patch for updating the language list dynamically. I checked the concerned patches and none of them were in the state of getting accepted.

hey @Gopavasanth thanks for the feedback. I have updated the proposal accordingly. Please have a quick go through and do leave some feedback points if something doesn't feel right :)
pinging @Soda for the same.