Crosswatch is giving a server error, can't reach the server. Something wrong with the way it contacts the databases?
This task is vague enough that it's probably about something else than I expected in my last comment, namely that after logging in via OAuth, I get the following error:
No watchlist could be retrieved. This is an internal server error, please open a bug report if the problem persists.
Server failure No watchlist could be retrieved. This is an internal server error, please open a bug report if the problem persists.
Tailing all of the obvious error log files in /data/project/crosswatch provides no useful data. The tool itself is licensed under an OSI-approved license so if the Tool Labs community approves a solution for T87730: Set up process / criteria for taking over abandoned tools which is currently being voted on at meta then it may be possible for a group of interested developers to jump in an try to debug further.
According to https://tools.wmflabs.org/?tool=crosswatch, @Sitic is the only maintainer of the current tool, and they have not responded to this bug in the last 5 months. I don't think raising the priority is going to change that, but I would love to be proven wrong.
Luckily the source is available (rTCRW labs/tools/crosswatch) and has a clear license. This gives the opportunity for an interested volunteer to step up and attempt to replace the tool with a fork. The more drastic step of requesting adoption of the existing tool is also available, but I'd recommend at least proving that a working version can be built before jumping into that discussion with the Toolforge-standards-committee.
Hey everyone, I started looking into this, there were quite a few problems to get a local version running, mostly due to old / incompatible / non-existent packages
I got a version working using Docker here - https://github.com/OriHoch/wikimedia-crosswatch/commit/cbe43385e749ca22ba4e7e7fe757121a19103740
I couldn't get the frontend assets to build, so I just downloaded the compiled assets from the live site and using them (hopefully, won't have to do any frontend fixes, as problems appears to be on server-side)
Now, I just need access to toolforge so I can test and fix this problem.
Alternatively - is there a way to test toolforge locally?
To get access to toolforge, see https://wikitech.wikimedia.org/wiki/Help:Getting_Started
That doesn't give you access to the tool itself, but as said, better to just get it working first, maybe on a second tool-account, for the toolforge basics see https://wikitech.wikimedia.org/wiki/Help:Toolforge
Once working you might request to take over the tool-account.
Good luck, and thanks for the willingness to look into this.
crosswatch uses an oauth consumer key for login, all docs seem to point to this page to request a key, but it is not available (I'm getting unauthorized on that page): https://meta.wikimedia.org/wiki/Special:OAuthConsumerRegistration/propose
any help would be appreciated
Are you getting unauthorized when submitting the form or you can not see the form on that page at all? Have you got the Toolforge membership already (https://wikitech.wikimedia.org/wiki/Help:Getting_Started#Get_started_with_Toolforge)?
Hi, sorry for the delay in reply. The problem was that the page is accessible only after making 5 edits on meta.wikimedia..
I got what I need now, hopefully I'll have some updates on this issue soon
I published some fixes here: https://github.com/OriHoch/wikimedia-crosswatch/commits/master
I deployed it but there are still some problems: https://crosswatch.k972il.com/crosswatch/
- waiting to get oauth consumer request to be approved - until it's approved you will get permission denied error for viewing your watchlist
- code for getting list of user wikis needs to be fixed, currently it's hard-coded to use en and he wikis for testing
To overcome the problem with getting list of user wikis I added a manual wiki selection page which appears after log-in
You have to input a list of wiki ids which you have a watchlist for. To change the wiki selection, log-out and back in.
My oauth consumer request is not approved yet, but it works for me.
It is deployed here: https://crosswatch.k972il.com/crosswatch/
The deployment is based on a Helm chart, in case you want to deploy on wikimedia infrastructure: https://github.com/OriHoch/wikimedia-crosswatch/tree/master/helm/crosswatch
This is the pending oauth request: https://meta.wikimedia.org/wiki/Special:OAuthListConsumers/view/28e50e47bd2b58e5a2f14d6bfbd7ecb7
@OriHoch I'm so happy you decided to take on fixing this tool! Having so many different watchlists is a daily pain. Please keep it up!
Today I tried accessing https://crosswatch.k972il.com/crosswatch
However, for some reason, after a few reloads the Welcome screen loaded, but when I tried to "Sign in with OAuth" I got the following error:
"crosswatchfix" is not approved as a Connected App. Contact the application author for help.
I guess you're still working on this. Just wanted to give some feedback and thank you again and again for your effort!