Brad Murray
Brad Murray
Also running into this. Seems like I'm only running into issues when using ts-loader in my webpack config. Example minimal repo reproducing the issue: https://github.com/bradtgmurray/babel-styled-components-test-repo  This branch fixes the...
I've gotten it to work again by swapping `--profile --json` to `--stats=detailed --json` but I'm not sure if that's the canonical way of doing it.
The way I prefer to customize makefiles is by specifying the extra arguments on the command line. Command line variable assignments always override variable assignments in the makefile itself, regardless...
The new Mentor toolchain includes GCC 4.6.3, which already has that patch applied. The patch was just there to work around an issue in the old GCC 4.6.1 toolchain and...
Running into this (or something similar) as well: ``` Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/synapse/http/server.py", line 257, in _async_render_wrapper with trace_servlet(request, self._extract_context): File "/usr/local/lib/python3.8/contextlib.py", line 113, in __enter__ return...
I think I figured out what this is: When you're paginating back through a room and you hit a reply event that's outside of your current timeline set, the client...
Seeing this as well. VSCode: Version 1.18.1 (1.18.1) ``` $ phantomjs --version 2.1.1 ``` ``` ›To target: "{\"id\":6,\"method\":\"Debugger.setBreakpointByUrl\",\"params\":{\"urlRegex\":\"phantomjs:\\\\/\\\\/code\\\\/index\\\\.js\",\"lineNumber\":3,\"columnNumber\":0}}" ›From target: {"result":{"breakpointId":"/phantomjs:\\/\\/code\\/index\\.js/:3:0","locations":[{"scriptId":"4","lineNumber":3,"columnNumber":0}]},"id":6} ›To client: {"seq":0,"type":"response","request_seq":3,"command":"setBreakpoints","success":true,"body":{"breakpoints":[{"id":1000,"verified":true,"line":3,"column":1}]}} ›From client: setExceptionBreakpoints({"filters":["uncaught"]}) ›To target: "{\"id\":7,\"method\":\"Debugger.setPauseOnExceptions\",\"params\":{\"state\":\"uncaught\"}}"...
This seems to happen because the phantomjs process isn't closing correctly, and trying to open a second process gets this error. If I force kill any open phantomjs processes the...
Just wanted to jump in and thank @deepbluev7 for continuing to push this forward. We're using this functionality to enable notifications when someone reacts to one of the user's messages...
We're now running this in production, here's an example base push rule for our users where users get notifications for reactions, but only to their messages, and only in rooms...