Robert Groh

Hi @karasusan, thank you for your reply. I guess I can limit the ports, which will be functioning (and returned as SERVER CANDIDATES from the STUN service) via blocks by...

I also needed the development files of the plasma framework (package name: **libkf5plasma-dev**).

@peterhendrick, from what I understand your are using your normal (NOT-instrumented) sources to start your server via `npm start` on port 3000. Then you run the default task of gruntfile-e2e.js...

@pranavvarshney when I got the message `No coverage object in the browser.` it was always caused by running the un-instrumented source code (either server-backend or client-side javascript in the browser)....

Something fishy is going on, at first I could reproduce your problem, but after I installed the Selenium jars with `node_modules/protractor/bin/webdriver-manager update` I got other problems, which I also can`t...

From #198: > But the size might be misleading. The issue is that npm base64-encodes the tarball and adds metadata to it when publishing. So if your tarball is 54Mb,...

Hi whererhys, unfortunately I have similar problems, but as far as I know `reloadTasks` tries to find new grunt-tasks in *.js or *.coffeescript files in the specified directory. Therefore it...

Hi Santiago, I feel your pain, I took me a while to grok istanbul (and this grunt-plugin). Regarding your problem, there are two case for this error: - your test...

@reefath, no `reloadTasks` is need for normal test coverage - it is only used to test `grunt-istanbul` itself. As I stated above (quoting myself: https://github.com/taichi/grunt-istanbul/issues/16#issuecomment-48204815), either: > - your test...

I took a look into the [changes between proton-6.3-8 and proton-7.0-1](https://github.com/ValveSoftware/Proton/compare/proton-6.3-8...proton-7.0-1). And for my illiterate eye, only these two commits might give hints: - [Commit 3b9480 (Feb 11, 2022) -...