Tue, Jan 14
Thu, Jan 9
Dec 13 2019
Dec 12 2019
Dec 11 2019
Dec 10 2019
Dec 6 2019
Hey @Nuria, @Krinkle, I think it will be simple to patch this, my understanding from looking at the Mediawiki code is that we already have the code to work with cookies from the mw.cookie module. So the patch here is to the mw.user module, correct? (specifically mw.user.sessionId). Can I ask why this feature lives in mw.user? If there are other modules besides EventLogging that depend on it, then they should also be informed since session cookies will alter the persistence behavior vs sessionStorage. If there are no other modules depending on it, why is it in mw.user?
Dec 5 2019
An initial patchset is now available. Let's start discussing how to activate it in vagrant and so on. There are some unit tests coming but in the interest of getting review kicked off I have uploaded an initial patchset without them.
Nov 27 2019
Yeah! Exactly, which is why I'm curious how this will be used. Will engineers see the stack trace and then visit the line,column location in the minified production code and try to decipher it?
@fgiunchedi I'm curious about these stack traces. I think we may have covered this before, but in production the code is minified, right? So what parts of these stack traces are actually helpful to engineers? I guess i'm trying to understand the workflow.
Rough first patchset submitted to get the conversation started. Very little is certain here since this is essentially the MVP transplanted into core with very few alterations, so bring your opinion. Hopefully everybody involved will be generous with their input and we can iterate through various patchsets and get to something good.
Nov 26 2019
Nov 22 2019
Nov 21 2019
Adding @Ottomata and @Nuria for feedback and thoughts as we start thinking about the best way to do this. Past experience with the beta analytics cluster that you'd like to (or not like to) see repeated would be helpful. How is testing done for EventBus events? Do you have a vision or concept for how this should work?
If we can't come to any other consensus, I think the best compromise looks like primary/secondary. It's neutral enough that we can shape the definitions in documentation or conversation. It has the flavor of @Nuria's tier-ness ideas which I think is useful, but I don't know if that mapping will be durable in this particular location. They don't say much about access control on their own, and I think they communicate the wrong priority in some senses. But being boring counts for a lot, and maybe it will just not be that visible for people to get confused. If it gets out of control, we could always change them. I think the system would survive :)
Nov 20 2019
Hmm, I need to read more about this and see some more examples and we can follow up.
New perspectives for the new day:
Nov 19 2019
I'd like to see the schema repositories either bear a direct relation to the name of the EventGate instance that will probably be used, or bear no relation at all and be completely orthogonal (like @Ottomata's latest proposal attempts).