Outreachy Intern, Winter 2022
User Details
- User Since
- Oct 12 2022, 1:31 PM (82 w, 13 h)
- Availability
- Available
- LDAP User
- NicoleLBee
- MediaWiki User
- NicoleLBee [ Global Accounts ]
Feb 20 2024
Sep 18 2023
Hi, @nskaggs, thanks for the reports. (I'm sorry that it took me months to notice them.) Everything in the Toolhunt <--> Toolhub connection appears to be working at present, so I'm assuming that Toolhub was just down at the time you attempted to use the tool.
Getting to this somewhat late, but submissions are going through to Toolhub at present, so I have to assume that this was due to the Toolhub server being down at precisely the wrong moment.
May 25 2023
May 24 2023
May 23 2023
Date & time: Sunday, May 21st at 10:30 am EEST / 7:30 am UTC
Session Notes:
Session Notes:
Session Notes:
Session Notes:
Session notes: see next comment.
Session Notes:
Session Notes:
Session Notes:
Session Notes:
Session Notes:
Session Notes:
Session Notes:
May 21 2023
I should note that this branch is currently LIVE ON PRODUCTION, yes I know that's a bad idea but the problems with toolhunt-staging make it impossible for me to actually use it as a test environment.
May 20 2023
A lot has changed since I opened this PR; need to review and rebase.
I'm happy to report my success! PRs open at https://github.com/wikimedia/toolhunt/pull/61 for the backend and https://github.com/wikimedia/toolhunt-ui/pull/63 for the frontend.
This task addressed by https://github.com/wikimedia/toolhunt-ui/pull/63
This task addressed by https://github.com/wikimedia/toolhunt-ui/pull/63
May 17 2023
May 7 2023
Apr 24 2023
Apr 12 2023
Ooh, thanks as usual, @bd808
Apr 11 2023
We've been requested to close out pending Outreachy-specific tasks and now that the authentication issues have been resolved (and the other issues I was experiencing seem to have gone... dormant??), it seems like an appropriate time to do so.
PR merged
PR merged
PR merged
PR merged
The issue was in the[[ https://router.vuejs.org/guide/essentials/history-mode.html | history mode ]] that we were using with the Vue router. (In development it appears that Vite was taking care of this for us... in production, not so much.) By switching to WebHashHistory mode I've enabled reloads on production. The downsides are that the URLs are now kind of ugly and apparently this is bad for SEO, if we even care about such things.
Apr 9 2023
Apr 7 2023
Thank you again, @Damilare
Apr 6 2023
Waiting on approval of the backend PR. https://github.com/wikimedia/toolhunt/pull/58
One difference that I notice is that if I go directly to https://toolhunt-staging.toolforge.org/api/authorize (currently rigged to the demo tool) I get an HTML response, whereas if I go to https://toolhunt.toolforge.org/api/authorize I get a JSON response. I don't know if this is significant, but it is a difference that exists for reasons unknown to me, JSONs are involved, and I really am scraping the bottom of my "ideas" barrel.
I went to toolhunt-staging (the frontend half of our staging tool), and changed the value of the proxy uri (VITE_FLASK_BACKEND_URL) to point to toolhub-oauth-test (my toolhub-demo-gadget clone); set toolhub-oauth-test to redirect to toolhunt-staging and IT WORKS. I am able to log into Toolhunt by this method.
I reinstalled authlib and requests and got the same error, then stuck Toolhunt's credentials into Toolhunt-api-staging, changed the various URIs and redirects, and ended up with the same error again, so presumably, there's nothing wrong with the package installations in Toolhunt. (I had been toying with the idea of wiping the data and re-cloning it, reinstalling all of the packages, etc.)
I made a clone of the toolhub-demo-gadget and hooked it up to Toolhub, and it works, so clearly there is something wrong with my implementation. The search continues...
Apr 5 2023
Suffice it to say that this is a big problem that I don't know how to solve. The deployment to Toolforge has definitely required more fiddling than we anticipated (though the documentation is quite good, and if it took a while it was entirely my fault).
I've opened a PR to address this issue: https://github.com/wikimedia/toolhunt-ui/pull/59
So if I'm reading that correctly, it's failing because the response that it's getting cannot be parsed as a json?
Apr 4 2023
Nope, not done yet. See T334025
I'm experiencing the same issue with my new tools, toolhunt-staging and toolhunt-api-staging:
tools.toolhunt-staging@tools-sgebastion-10:~$ sql tools ERROR 1045 (28000): Access denied for user 's55383'@'172.16.6.95' (using password: YES)
tools.toolhunt-api-staging@tools-sgebastion-10:~$ sql tools ERROR 1045 (28000): Access denied for user 's55384'@'172.16.6.95' (using password: YES)
Apr 2 2023
The backend is now running with "production" values -- i.e., it's using data from our production database and getting information from the Toolhub servers.