(Photography by Niek Hidding.)
If the interface in question is not server-side rendered or if the query param otherwise does not varies the server response, and if sharing a link to the current tab is not yet possible (per the above comment). Then perhaps this might make more sense as a hash fragment? We could use something like #!/tab/foo for this purpose, although given it is a special page you might not need to worry about ambiguity with headings from user-generated content and could thus also use something simpler like #foo or #tab-foo. See Special:Preferences for an example of this.
I've uploaded a Tourbot pattern for the migration at https://github.com/Krinkle/mw-tool-tourbot/commit/fdfb13a95. After the above backport is deployed and wmf.2 has reached group2, then it can be used to start migrating usage.
Looks like a regression. Tagging CPT and SDT, not sure where this falls under. I suppose it depends on where the culprit lies, which itself first needs to be determined.
10 days have passed.
The master patch was backported to wmf.1 and +2'ed in master before wmf.2 was cut, but it got lost in Zuul land somehow. This must be deployed before group2.
Next step: In master (1.35):
- Remove the ProfilerOutputDb class,
- Remove the profileinfo.php entry point.
- Remove the profiling table schema definitions. (Document in the release notes that given it is mainly a developer feature, and the schema wasn't auto-created, it will also not be auto-removed. Anyone wishing to remove their old profiles can do so by running the DROP TABLE profiling; statement through sql.)
- Remove anything else internal that solely for making ProfilerOutputDb possible.
Performance has no opposition to enabling caching here for third parties. Makes sense to me. I've tagged CPT to further look at what the InstantCommons feature's needs are and whether it is functionally safe to re-enable, and what other (not perf-related) reasons there may be for keeping it off.
Looks like this has had an IRC meeting. Problem statement is clear. Proposal has been formed. No objections from TechCom and no stakeholders were identified beyond CPT and the various developers that have already participated so far.
Sorry about that. I missed that Will had just untagged CPT.
Can you check whether it works in latest Chrome when setting a breakpoint in a raw core file (with its version hash), and whether it remains after changing its content? I suspect this might work actually, and that the issue is with packageFiles having "load.php" as its filename which is ambiguous in this context (vs raw files having each their own url where the parameter can be ignored). In particular because a similar issue mentioned at T90983#2083366 was fixed upstream in Chromium.
Moving from tracked under "Stuff part of deploying PHP 7 properly" to instead above "Stuff unblocked by not having HHVM".
Interesting, that seems like a bug. Possibly configuration related.
I thought maybe it was user-permission or working-directory related. But, looks like not.. As www-data and from a different directory, it also works fine via CLI:
I fiddled around a bit and found something that might work. First, the outcome:
@Jdlrobson Can you clarify what problem this is meant to solve? The example link works as expected in Vector, by having 5 lines of CSS instead of 1. Not a huge cost, but I guess the intent is to reduce this somehow. The proposed core involves `1 line of CSS instead of 5, however it doesn't solve the same problem.
Tue, Oct 15
Review of overall approach on using YAML perf restrictions/flexibilities (e.g. what should def be cached, and what would be fine to do at run-time) now pencilled in for Q3, maybe Q2. Not expecting to involve TechCom or CPT right now, but depending on how ambitious we want to me, might make sense to involve or or both at some point, but hoping right now to keep it isolated enough to not be cross-cutting
Short-term decision based on today's meeting: Temporarily reduce retention from 90 days to 45 days. Hopefully only for a few weeks.
Re-opening since the "removal" part is still outstanding and will happen sometime this quarter during the 1.35 cycle.