-
-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Compatibility to wmf/1.43.0-wmf.1 #421
Comments
It looks like the Chameleon code is likely not even compatible with the future REL1_42 yet: #422 |
@malberts, Normally, these updates are easy to fix once you find the correct phabricator ticket, which I did not manage to do in a few minutes. |
For this particular problem, it's just this line Line 34 in 0225fb1
|
By the way... the phabricator ticket is https://phabricator.wikimedia.org/T166010 |
@JeroenDeDauw, what do you think? |
|
#423 might not be enough to solve the 1.42 compatibility. There are also ResourceLoader namespace changes in the SCSS dependency, and possibly our Bootstrap extension too. I am looking at those. |
@physikerwelt Can you try with the latest Chameleon master branch (which is going to be the new major version 5.0.0). I updated the Bootstrap and SCSS dependencies and CI now passes on MW 1.42 and MW master. However, I have not manually tested either of those unreleased MW versions. |
Thank you. This is a great improvement. A quick update from our side: We updated to the latest master today at 3am. https://staging.mardi4nfdi.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&safemode=1 does produce an invalid result:
This might be unrealated... however, I just had 20 minutes for this task today and wanted to share the preminar good result with you anyhow. |
Thanks @physikerwelt. That |
We see the following error
on https://staging.mardi4nfdi.org/wiki/Model_for_Electric_Potential_for_Gate_Electrodes_in_a_Quantum_Bus after upgrading to the latest production release. I wonder if this skin is deployed on any wiki that follows the WMF release cycle, as the root cause for the problem might also be somewhere else.
The text was updated successfully, but these errors were encountered: