Simon Frei

Actually when looking into something else, I noticed the a flood of `events` GET requests: Apparently there's a constant stream of successfully login attempt events when having the GUI open....

Weird indeed - every response to the events endpoint gets a new session with the "set-cookie" header in the response. However while I can repro at will in "normal" firefox...

There are already two benchmark tests in the lib/ignore package - not sure how good/representative they are but probably good for a first check.

Did you look at the cached benchmark, possibly? The other one is roughly a factor 4 slower. Not quite a magnitude, but significant. I see you already opened a ticket...

That warning comes up on every restart. I would like that too, but I think there have been previous discussions on this and the project consensus was that it should...

`-no-restart` does not control if there is a monitor process since quite a while: There always is a monitor process (e.g. for panic handling). And the monitor stops the child...

> I guess then that the information from https://docs.syncthing.net/includes/env-vars.html?highlight=stnorestart is outdated also, right? Yes it is. I don't think there's anything we can do here. The best info I found...

I took the liberty of repurposing this issue as there is no bug and opened an issue on the docs repo: https://github.com/syncthing/docs/issues/577

This has already been discussed as part of #2491. However I think it's useful to have this as a separate issue, as it's doable with how ignore patterns work currently....

I would have bet on us having this issue already, but I can't find anything. Would definitely be useful! Walking through setting up a folder would be much bettern than...