@Reputation22 I think @Aditiganvir28 was working on this ?

In T332517#8714804, @Aditiganvir28 wrote:

Hey @Soda @Gopavasanth My frontend and backend both are running and also nginx is running successfully but I am getting 502 bad gateway error on localhost:8000 (proxy server) . Can you please guide me what should I do

Thanks for the report, I have restarted the containers

@Reputation22 Can you explain what you mean by trimming from the left, I can't seem to be able to get the tool to trim from the left, not sure if I'm doing anything wrong ?

In T332517#8709117, @AFZL210 wrote:

@Soda If I'm not mistaken, what we want is to first build the React frontend code, and then serve it from the root route '/' while using a prefix like '/api' for backend-related tasks on the same port

@Najni_Fatima Lmk if you are stuck in a specific area

Not really, best to add a link to this in the README ? (Or maybe better to document this specific instance in the README itself)

Lets not decline this :)

Use the Wikimedia Parsing text API (https://m.mediawiki.org/wiki/API:Parsing_wikitext) or the Parsoid Rest API

Seems like a good idea :)

Looks like sequelize doesn't play well with ESM modules, we should probably switch to CommonJS modules for now

I do intend to use seqelize to make for easier migration from Mongo

Thanks for the patch

Lets branch out the session storage aspect into a different bug though

In T330755#8670710, @Reputation22 wrote:

In T330755#8670701, @Soda wrote:

In T330755#8665936, @Reputation22 wrote:

We can go with PostgreSQL, and for in-memory we can opt for Redis.

I don't think we want a in-memory solution, I'll tryout PostgreSQL since I'm dealing working with it right now IRL (I can set it up without too much issue).

how are we planning to store the cookies and sessions, via postgres?

In T330755#8665936, @Reputation22 wrote:

We can go with PostgreSQL, and for in-memory we can opt for Redis.

In T331233#8666930, @Punith.nyk wrote:

you(@Soda) mean for this particular video ->https://commons.wikimedia.org/wiki/File:%27Walla_Zaman_Ya_Selahy%27.ogg
{{self|cc-by-sa-4.0}} should be replace by the text given below

should be {{Text}} or {{self| Text}} or just Text

Also we should be able to avoid these issues after https://gerrit.wikimedia.org/r/c/labs/tools/VideoCutTool/+/894169 is merged (which moves the environment variables into a .env file that is ignored by git via .gitignore)

@Aklapper Those are local credentials for setting up a development environment, and are not the ones used by VideoCutTool on Toolforge (AFAIK). The callback URL for those keys are set to http://localhost:4000/api/auth/mediawiki/callback which shouldn't be reachable by anyone except the user themselves. (This is the associated grant based on some digging around: https://meta.wikimedia.org/w/index.php?title=Special:OAuthListConsumers/view/fe3623a2f263e7f95ae8b602641f2415&name=Akash+Ranja&publisher=&stage=1)

This sounds like a good idea, feel free to ping us (me/@Gopavasanth) if you are getting stuck anywhere

I think @KunalKatara12 is still working on this, so this isn't open right now. (Btw, feel free to ping us (me/@Gopavasanth) if you get stuck anywhere @KunalKatara12 )

In T330755#8660010, @Gopavasanth wrote:

I would choose SQLite because of its excellent administrative features and the ease of implementing and utilizing an in-memory database.

This probably isn't ProofreadPage, WS Export looks like the proper project :)

Right, I think we can probably investigate PostgreSQL and/or SQLite with a sequelize ORM for our current needs given that no NoSQL databases are supported. (ping @Gopavasanth in case they have any thoughts on other ORMs/other alternative databases to use)

@taavi Are there any alternatives (NoSQL databases that are interoperable with NodeJS) that we can shift to that are offered by the WMCS ?

Removing assignee, pls read the top info text (this is umbrella microtask so please don't assign yourself the task but feel free to work on it)

Sure, that sounds great, I am interested in taking up the role (also thanks for the kind words 🙂)

In T264878#8641844, @Najni_Fatima wrote:

@Gopavasanth @Soda
After Drag and drop from user's devices to VideoCutTool for editing. The video is not actually getting uploaded (according to the code). So why are we adding a progress bar here?

In T330093#8637053, @zeljkofilipin wrote:

Additionally, when I try to run the tests from a Fresh container, I get ERROR @wdio/config:ConfigParser: Failed loading configuration file: /ProofreadPage/tests/selenium/wdio.conf.js: ENOENT: no such file or directory, open '/LocalSettings.php'.

P44730 ProofreadPage$ npm run selenium-test

1	z@imac-ubuntu:~/Documents/gerrit/mediawiki/core/extensions/ProofreadPage$ fresh-node14 -env -net
2	# fresh: 22.11.1
3	# image: docker-registry.wikimedia.org/releng/node14-test-browser:0.0.2-s4
4	# software: Debian GNU/Linux 11 (bullseye)
5	# Node.js v14.17.5 (npm 7.21.0)
6	# Chromium 97.0.4692.99
7	# Mozilla Firefox 91.5.0esr
8	# JSDuck 5.3.4 (Ruby 2.7.4) ruby 2.7.4p191
9	# mount: /ProofreadPage ➟ /home/z/Documents/gerrit/mediawiki/core/extensions/ProofreadPage (read-write)
10	# /ProofreadPage/.git ➟ /home/z/Documents/gerrit/mediawiki/core/extensions/ProofreadPage/.git (read-only)
11	# env: MW_*, MEDIAWIKI_*
12	# net: expose host
13
14	🌱 Fresh!
15
16
17
18	I have no name!@imac-ubuntu:/ProofreadPage$ npm run selenium-test
19
20	> selenium-test
21	> wdio tests/selenium/wdio.conf.js
22
23	2023-02-22T12:25:59.207Z ERROR @wdio/config:ConfigParser: Failed loading configuration file: /ProofreadPage/tests/selenium/wdio.conf.js: ENOENT: no such file or directory, open '/LocalSettings.php'
24	wdio [command]
25
26	The `wdio` command allows you run and manage your WebdriverIO test suite.
27	If no command is provided it calls the `run` command by default, so:
28
29	$ wdio wdio.conf.js
30
31	is the same as:
32	$ wdio run wdio.conf.js
33
34	For more information, visit: https://webdriver.io/docs/clioptions
35
36	Commands:
37	wdio config Initialize WebdriverIO and setup
38	configuration in your current project.
39	wdio install <type> <name> Add a `reporter`, `service`, or `framework`
40	to your WebdriverIO project. The command
41	installs the package from NPM, adds it to
42	your package.json and modifies the
43	wdio.conf.js accordingly.
44	wdio repl <option> [capabilities] Run WebDriver session in command line
45	wdio run <configPath> Run your WDIO configuration file to
46	initialize your tests. (default)
47
48	Options:
49	--help Show help [boolean]
50	--version Show version number [boolean]
51	--watch Run WebdriverIO in watch mode [boolean]
52	-h, --hostname automation driver host address [string]
53	-p, --port automation driver port [number]
54	--path path to WebDriver endpoints (default "/") [string]
55	-u, --user username if using a cloud service as automation backend
56	[string]
57	-k, --key corresponding access key to the user [string]
58	-l, --logLevel level of logging verbosity
59	[choices: "trace", "debug", "info", "warn", "error", "silent"]
60	--bail stop test runner after specific amount of tests have
61	failed [number]
62	--baseUrl shorten url command calls by setting a base url[string]
63	-w, --waitforTimeout timeout for all waitForXXX commands [number]
64	-f, --framework defines the framework (Mocha, Jasmine or Cucumber) to
65	run the specs [string]
66	-r, --reporters reporters to print out the results on stdout [array]
67	--suite overwrites the specs attribute and runs the defined
68	suite [array]
69	--spec run only a certain spec file - overrides specs piped
70	from stdin [array]
71	--exclude exclude certain spec file from the test run - overrides
72	exclude piped from stdin [array]
73	--mochaOpts Mocha options
74	--jasmineOpts Jasmine options
75	--cucumberOpts Cucumber options
76	--autoCompileOpts Auto compilation options
77
78	Examples:
79	wdio run wdio.conf.js --suite foobar Run suite on testsuite "foobar"
80	wdio run wdio.conf.js --spec Run suite on specific specs
81	./tests/e2e/a.js --spec ./tests/e2e/b.js
82	wdio run wdio.conf.js --spec Run scenario by line number
83	./tests/e2e/a.feature:5
84	wdio run wdio.conf.js --spec Run scenarios by line number
85	./tests/e2e/a.feature:5:10
86	wdio run wdio.conf.js --spec Run scenarios by line number in
87	./tests/e2e/a.feature:5:10 --spec single feature and another complete
88	./test/e2e/b.feature feature
89	wdio install reporter spec Install @wdio/spec-reporter
90	wdio repl chrome -u <SAUCE_USERNAME> -k Run repl in Sauce Labs cloud
91	<SAUCE_ACCESS_KEY>
92
93	Documentation: https://webdriver.io
94	@wdio/cli (v7.3.0)
95
96	Error: ENOENT: no such file or directory, open '/LocalSettings.php'
97	at Object.openSync (fs.js:498:3)
98	at Object.readFileSync (fs.js:394:35)
99	at Object.<anonymous> (/ProofreadPage/tests/selenium/wdio.conf.js:10:33)
100	at Module._compile (internal/modules/cjs/loader.js:1072:14)
101	at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
102	at Module.load (internal/modules/cjs/loader.js:937:32)
103	at Function.Module._load (internal/modules/cjs/loader.js:778:12)
104	at Module.require (internal/modules/cjs/loader.js:961:19)
105	at require (internal/modules/cjs/helpers.js:92:18)
106	at FileSystemPathService.loadFile (/ProofreadPage/node_modules/@wdio/config/build/lib/FileSystemPathService.js:22:16)
107	exit

In T330093#8637035, @zeljkofilipin wrote:

Hi @Soda! I've tried adding the variable to LocalSettings.php (diff) but I'm getting the same results. Did I misunderstood what needs to be done?

I don't think @I has access to the LogStash (for that matter, I don't think anyone who will be browsing good first task will have the requisite access)

In T262895#8626331, @Punith.nyk wrote:

Hey, @Gopavasanth @Soda Is this task all about filling the comment section of the result page to the videos which doesn't have comment text right ?

Wrt to P17185, currently the feature being tested via Selenium is behind the $wgProofreadPageEnableEditInSequence feature flag. Setting it to true should allow the tests to run locally.

@zeljkofilipin I've been working on ProofreadPage selenium tests, will be happy to answer questions on test and general ProofreadPage setup.

@I The discussion you linked started today and has very few participants, I'd defer untill we have participants in the discussion/the discussion has been open for a sufficiently long time without any opposing remarks before making the change :)

In T308824#8615862, @Punith.nyk wrote:

Hey, @Gopavasanth you basically want the tooltip representing the time

to be editable right?

@ShreyashPingle Let me know if your are interested in working on this task wrt to testing the Mongoose model, I can try and take a stab at helping you integrate it with CI.

@ShreyashPingle Please take a look at T328928

In T272955#8614673, @ShreyashPingle wrote:

Hey @Gopavasanth I have written a mocha test to test the mongoDB connection.

it passes the test should I create a patch for it ?

Imo we should not be using Mocha, since we plan to use to Jest for the frontend we should also use jest for the backend. It doesn't make sense to have two types of testing systems on the same project :(

In T275491#8593594, @DishaJain01 wrote:

In T328928#8590210, @Sidharthkumar23 wrote:

Hi, I would like to work on this issue. Could you please assign this to me?

Hey @Sidharthkumar23 this is somewhat of a umbrella task of sorts so I'm not assigning it to a specific contributor, but feel free to work on it :)

In T327582#8589344, @Vishudhiman1900 wrote:

hey hie, I would like to work on "Support to persist the edited video after the tab refresh."
can yu please assign this to me?

In T275491#8587781, @DishaJain01 wrote:

Sir,can you please assign this task to me?

In T328394#8587267, @DishaJain01 wrote:

Hello Sir,Can you please assign this task to me?And can you please tell us where we can find the code for the above bug?I want to contribute.
Thanks

@Punith.nyk Can you give some more information on how this behaviour can be reproduced ?

@Reputation22 It would make sense to add some verbiage to ask users to report the issue to phabricator if the error is not expected :)

In T276665#8567637, @Reputation22 wrote:

In T276665#8565751, @Soda wrote:

In T276665#8565673, @Reputation22 wrote:

Here's how it looks, how and where should I submit the PR regarding this?

It seems a bit mystery meat right now, maybe we can add it as part of the button ? (Preview <number> of features)

hey @Soda, i have a doubt, changing the text of the preview button can be done in the languages json files, so should i manually update the id for the message for all the language json files, or will it change it automatically for me?

In T283414#8567442, @Gopavasanth wrote:

Hi @Punith.nyk, It would be great if we have direct upload functionality as well without editing. We can probably take the filename as the video name and provide an option to user to edit required fields similar to the current method of uploading video to the commons.

In T234783#8567269, @Punith.nyk wrote:

@Reputation22 The work is half done I am on just want to confirm the sender's address (official email address videocuttool) with @Gopavasanth /@Soda

I don't think using the sender's address in this case is the way to go, instead, I think we should use the Wikimedia email API to send emails to the user (we can eithier create a new user account for this, or opt to have the new user email themselves via the OAuth sendemail permission).

In T276665#8565673, @Reputation22 wrote:

Here's how it looks, how and where should I submit the PR regarding this?

In T308914#8541307, @Punith.nyk wrote:

Hey @Gopavasanth, I came up with a solution for this issue. So, whenever the user gives an incorrect request, we navigate them back to the homepage.
let me know if it suits, I will create a patch for it.

In T327344#8542117, @Nux wrote:

I have a workaround that works for me on V22:
https://pl.wikisource.org/w/index.php?title=Wikiskryba:Nux/common.css&oldid=3224317#L-23

That didn't cause any problems for me so far, but I'm not a very active WS editor.

This would be the correct solution, except that it clashes with the (current under development) edit-in-sequence preview module :(

This is caused by the fact that we use the height of the image as the size of the editform :(

In T327344#8538477, @Wieralee wrote:

My view of this page is "better". And all pages opened simultaneously with this one have the same weird size :((

Can you explain what you mean by this ? The size is not supposed to persist across sessions/tabs (and that would probably require filing a seperate task)

In T323847#8503555, @Nux wrote:

@Soda seems like there is an unresolved discussion here:
https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikisource/+/861348/

Looks resolved to me, but idk. Maybe you just forgot to change status? :)

Wrt to Layout storage, maybe once we implement T294903 we will be able to directly allow users to send layout data ?

Currently the basic MVP should work on Beta Wikisource, mostly.