Hey,
I am new to open source contribution and want to resolve the bug . I have following queries regarding it:
In this I have to change the heading and title of page. Anything else I need to do?

Please suggest me with how should I proceed?

@DannyH suggested (analogous to the message used for regular pages):

Revision history of Topic on $1

The $1 parameter should be the full board name, e.g. Talk:Flow.

I think this should be used for both the document title and the <h1>.

Can this get assigned to me? Its been quite a time the assignee has claimed this task . I'd like to patch on this one.

HI , which repo should I browse the code exactly in. I've installed and run mediawiki on my local machine both manually as well as with mediawiki-vagrant . They render the regular pages for revision history .How do I switch to the wikipedia 'variant/role' to recreate the situation as mentioned the in the description on my local installation ?

This is a StructuredDiscussions task, so you would need to enable the 'flow' vagrant role. Once you do that and then vagrant provision, Flow should be cloned into extensions/Flow under the mediawiki directory, and that is where you will need to make changes.

My vagrant installation always return either the "stack overflow" or "503 service unavailable error" whenever I request 127.0.0.1:8080 . I;ve wasted 3 nights straight for this frustating conclusion .
I've cloned it as "git clone --recursive ssh://dg7@gerrit.wikimedia.org:29418/mediawiki/vagrant " now .
It worked fine for once when I initially installed it by cloning "git clone --recursive https:gerrit.wikimedia.org/mediawiki/vagrant " , But I wouldn't have the commit access with that clone .

Should I just go with manual installation ?

In T72472#1947052, @dg711 wrote:

My vagrant installation always return either the "stack overflow" or "503 service unavailable error" whenever I request 127.0.0.1:8080 . I;ve wasted 3 nights straight for this frustating conclusion .
I've cloned it as "git clone --recursive ssh://dg7@gerrit.wikimedia.org:29418/mediawiki/vagrant " now .
It worked fine for once when I initially installed it by cloning "git clone --recursive https:gerrit.wikimedia.org/mediawiki/vagrant " , But I wouldn't have the commit access with that clone .

Sorry it's not working yet.

You can change the URL of an existing clone with:

git remote set-url origin ssh://dg7@gerrit.wikimedia.org:29418/mediawiki/vagrant.git

Run:

PUPPET_DEBUG=true vagrant provision|tee debug_output.log

then post the debug_output.log.

Also post a screenshot of the error you see in the browser.

In T72472#1947052, @dg711 wrote:

Should I just go with manual installation ?

That's an option, if you're familiar with LAMP steps. Some members of our team do that, but you will not be able to pick up Vagrant fixes and troubleshooting might be more difficult (or not).

Well, I use windows actually , so its WAMP for me . Should have switched to linux earlier :/

I'll give a few more attempts ASAP I get sufficient time .

In T72472#1957331, @dg711 wrote:

Well, I use windows actually , so its WAMP for me . Should have switched to linux earlier :/

Oh. MediaWiki-Vagrant is not well tested on Windows hosts (though we would still like it to work).

So, I started from the scratch to avoid any error caused by myself earlier . Cloned it as -> ssh://dg7@gerrit.wikimedia.org:29418/mediawiki/vagrant.git

Now ,on vagrant up , it clones the mediawiki as well as other repositories via https only ,i.e, https://gerrit.wikimedia.org/r/p/mediawiki/core.git ( no commit access) .
How should I go about it ?

the log gives the following message at last : The SSH command responded with a non-zero exit status ........

The code loads on requesting 127.0.0.1:8080 , The only problem presently is with this SSH issue .

So, it runs like this with just monobook role enabled .
The screenshot :

Now, when I enabled and provisioned for "Flow" role along with monobook , it all broke when I executed "vagrant reload".
screenshot :

Both pastes are 404 now.

Use https://phabricator.wikimedia.org/paste/create/ (still separate paste for each) so they don't disappear.

Provision : https://phabricator.wikimedia.org/P2530
Reload : https://phabricator.wikimedia.org/P2529

The relevant parts are

==> default: Notice: /Stage[main]/Role::Echo/Mysql::Sql[create echo_unread_wikis]/Exec[create echo_unread_wikis]/returns: ERROR at line 1: Failed to open file '/vagrant/mediawiki/extensions/Echo/db_patches/echo_unread_wikis.sql', error: 2
==> default: Error: /Stage[main]/Role::Echo/Mysql::Sql[create echo_unread_wikis]/Exec[create echo_unread_wikis]/returns: change from notrun to 0 failed: /usr/bin/mysql -uroot -pvagrant -qfsAe "USE wikishared; SOURCE /vagrant/mediawiki/extensions/Echo/db_patches/echo_unread_wikis.sql;" returned 1 instead of one of [0]

and (redacted)

Loading composer repositories with package information
Installing dependencies (including require-dev)
  - Installing squizlabs/php_codesniffer (2.5.0)
    Cloning e4fb41d5d0387d556e2c25534d630b3cce90ea67
    Failed to download squizlabs/php_codesniffer from source: The process "git clone --no-checkout 'git://github.com/squizlabs/PHP_CodeSniffer.git' '/vagrant/mediawiki/extensions/SyntaxHighlight_GeSHi/vendor/squizlabs/php_codesniffer' && cd '/vagrant/mediawiki/extensions/SyntaxHighlight_GeSHi/vendor/squizlabs/php_codesniffer' && git remote add composer 'git://github.com/squizlabs/PHP_CodeSniffer.git' && git fetch composer" exceeded the timeout of 300 seconds.
    Now trying to download from dist
  - Installing squizlabs/php_codesniffer (2.5.0)
  [RuntimeException]                                                                                                                         
  Could not delete 
==> default: Error: /Stage[main]/Role::Geshi/Mediawiki::Extension[SyntaxHighlight_GeSHi]/Php::Composer::Install[/vagrant/mediawiki/extensions/SyntaxHighlight_GeSHi]/Exec[composer-install--vagrant-mediawiki-extensions-SyntaxHighlight_GeSHi]/returns: change from notrun to 0 failed: /usr/local/bin/composer install --optimize-autoloader --prefer-source returned 1 instead of one of [0]

The first is an echo bug, the second maybe a combination of a network issue and a vagrant file permissions issue? You might have to run Composer manually to clean up.

In T72472#1968112, @Tgr wrote:

The first is an echo bug, the second maybe a combination of a network issue and a vagrant file permissions issue? You might have to run Composer manually to clean up.

It doesn't seem like an Echo bug per se to me. It seems like you don't have db_patches/echo_unread_wikis.sql (which is in Echo master) for some reason. Try updating Echo to latest master before trying again. This worked for other people.

It doesn't seem like an Echo bug per se to me. It seems like you don't have db_patches/echo_unread_wikis.sql (which is in Echo master) for some reason. Try updating Echo to latest master before trying again. This worked for other people.

So , should I just have to rebase my local repo now ?

I did a "git rebase.." and "vagrant up" with flow role enabled and it worked somehow . But , I didn't find any effect of Flow .
I checked the LocalSettings.php in vagrant/mediawiki/ repo and couldn't find any

require_once "$IP/extensions/Flow/Flow.php";

So, do I have make these changes manually ? Or was Vagrant supposed to do that ?

In T72472#1980177, @dg711 wrote:

So, do I have make these changes manually ? Or was Vagrant supposed to do that ?

Flow should be working, and settings.d/puppet-managed/20-Flow.php should have been automatically created.

The easiest way to test Flow out of the box is to go to Flow_test:Whatever or Flow_test_talk:Whatever (any page name in those namespaces works).

You can also (as Admin) use Special:EnableFlow to enable Flow on absolutely any page.

@dg711: This issue has been assigned to you a while ago.
Could you please share a status update? Are you still working (or still plan to work) on this issue? Is there anything that others could help with? If you do not plan to work on this issue anymore, please remove yourself as assignee (via Add Action... → Assign / Claim in the dropdown menu) so others could work on it. Thanks a lot!

Is this issue still open? Can I work on it?

@Swayamsrk it's open, but it's not a high priority item and Flow is in maintenance mode, so I would maybe look for a different task to work on.