Jason Greathouse

Settings were something like: ``` "sync-rsync.sites": [ { "remotePath": "" } ], "sync-rsync.delete": true, "sync-rsync.onSave": true ``` OS: Ubuntu 21.04 vscode: 1.62 (ish)

https://github.com/thisboyiscrazy/vscode-rsync/blob/90ae7c488fa2a478cc385a5619fe4eba847dbbe7/src/Config.ts#L126 Is the culprit. Since "" does not equal `null`, you're defaulting to `/`. :cry:

Can I ask a question here? Would this feature be more likely to be approved and merged if it wasn't tied to the --dry-run flag? I can't speak for everyone,...

I'm also hitting this issue with an upgrade to 4.19.0 4.18.2 does not have this issue.

This might be clear to others, but the key here is that if you use the automatically generated labels `[self-hosted, Linux, X64]` as part of the `runs-on` array, you must...

> Hey @jgreat, > > Is it possible that fnv hash of these two namespaces has collisions? The listener name is computed [here](https://github.com/actions/actions-runner-controller/blob/d72774753c1ac24f927cac68b368f2abc9f65f40/controllers/actions.github.com/resourcebuilder.go#L655). From the log, it seems to me...

Still an issue, please do not close.