Stefan Becker

I can confirm this issue. I'm using `react-input-range` version 1.3.0. To avoid the React warning I have updated my `onChange` callback to ignore invalid values: ```javascript constructor(props) { ... this.changed...

I ran into the same issue. ***BUT*** ~~in my case I can't reproduce it on development code, i.e. in the Dev Env of my app, only on production code, i.e....

As a workaround for this problem I now make sure that the notification is removed in my helper function. Here is the gist of the code: ~~~js const makeNotification =...

+1 Just ran into the same issue with another git repo web viewer. Wrapping the markdown-toc tags in `[comment]: # (...)` would fix this. I use that "trick" for all...

Sorry for my bad Pythonese. Your solution using `cmd_quote` is much better. I tested your latest change and it doesn't handle all cases correctly. Please see the latest commit I...

@chpio I noticed that too and fixed it in my patch stefanb2@d1583d5b

@muayyad-alsadi oops I just looked at the generated command lines and missed the fact that your are **not** passing them to the shell. Just forget my change then.

@bkueng the value for `flat-manager-url` is a guess. I have been unable to find any documentation for the API URL of the Flathub repository.

As a side note: I think this code in `nmbs_server_poll()` may not work as expected, because `send_exception_msg()` returns the result from `send_msg()` and not the exception error code itself: ~~~c...

The proposed PR fixes the problem for me, but I have client code disabled.