[15:23:47] <anomie>	 MatmaRex: I may have found where your JS is synthesizing that {"error":{"info":""}} response.
[15:24:21] <MatmaRex>	 anomie: yeah, i was just reading my emails
[15:25:09] <MatmaRex>	 anomie: i thought that {foo: undefined} stringifies to "{"foo": undefined}", not to "{}". grumble
[15:25:42] * anomie has no idea about that
[19:15:23] <ostriches>	 I could use some Opinions on https://phabricator.wikimedia.org/T137901
[19:15:34] <ostriches>	 I can't decide if it's a regression or not without some kind of full stack trace.
[19:16:01] <ostriches>	 Code definitely allows the error (and likely has for some time), but I'm not sure if it's an actual blocker to 1.27
[19:35:31] <ostriches>	 *crickets*
[19:42:21] <MatmaRex>	 i agree with you, can't decide without some kind of full stack trace.
[19:42:23] <MatmaRex>	 :>
[19:49:12] <ostriches>	 "No editing activity" doesn't mean much though.
[19:49:29] <ostriches>	 Could be job queue, or reads easily enough
[19:50:48] <anomie>	 ostriches: Seems unlikely to be a regression in Parser itself, at any rate, since the code in question has been there since 1.25.
[19:51:02] <ostriches>	 Yeah, I don't think it's anything within the parser.
[19:52:21] <ostriches>	 Nothing in the preprocessor has changed here recently either
[19:52:46] <ostriches>	 I suspect either TraditionalImageGallery or some extension
[19:53:45] <ostriches>	 Again, can't tell without a backtrace :)
[19:56:00] <ostriches>	 E_NEEDMOREINFO from OP :)
[19:58:26] <ostriches>	 Calling function on null are hard to track down on super-open objects like parser :\