-
v1.4.1
v1.4.1 This is a regularly scheduled patch release. Bugfixes: - #6289: "general SOCKS server failure" since syncthing 1.3.3 - #6365: Connection errors not shown in GUI - #6415: Loop in database migration "folder db index missing" after upgrade to v1.4.0 - #6422: "fatal error: runtime: out of memory" during database migration on QNAP NAS Enhancements: - #5380: gui: Display folder/device name in modal - #5979: UNIX socket permission bits - #6384: Do auto upgrades early and synchronously on startup Other issues: - #6249: Remove unnecessary RAM/CPU stats from GUI
-
v1.4.1-rc.3
v1.4.1-rc.3 This is a release candidate for the v1.4.1 patch release. Bugfixes: - #6289: "general SOCKS server failure" since syncthing 1.3.3 - #6365: Connection errors not shown in GUI - #6415: Loop in database migration "folder db index missing" after upgrade to v1.4.0 - #6422: "fatal error: runtime: out of memory" during database migration on QNAP NAS Enhancements: - #5380: gui: Display folder/device name in modal - #5979: UNIX socket permission bits - #6384: Do auto upgrades early and synchronously on startup Other issues: - #6249: Remove unnecessary RAM/CPU stats from GUI
-
v1.4.1-rc.2
v1.4.1-rc.2 This is a release candidate for the v1.4.1 patch release. Bugfixes: - #6289: "general SOCKS server failure" since syncthing 1.3.3 - #6365: Connection errors not shown in GUI - #6415: Loop in database migration "folder db index missing" after upgrade to v1.4.0 - #6422: "fatal error: runtime: out of memory" during database migration on QNAP NAS Enhancements: - #5380: gui: Display folder/device name in modal - #5979: UNIX socket permission bits - #6384: Do auto upgrades early and synchronously on startup Other issues: - #6249: Remove unnecessary RAM/CPU stats from GUI
-
v1.4.1-rc.1
v1.4.1-rc.1 This is a release candidate for the v1.4.1 patch release. Bugfixes: - #6289: "general SOCKS server failure" since syncthing 1.3.3 - #6365: Connection errors not shown in GUI - #6415: Loop in database migration "folder db index missing" after upgrade to v1.4.0 - #6422: "fatal error: runtime: out of memory" during database migration on QNAP NAS Enhancements: - #5380: gui: Display folder/device name in modal - #5979: UNIX socket permission bits - #6384: Do auto upgrades early and synchronously on startup Other issues: - #6249: Remove unnecessary RAM/CPU stats from GUI
-
v1.4.0
v1.4.0 This is a regularly scheduled minor release. Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 - #6304: Syncing issues, database missing sequence entries - #6335: Crash or hard shutdown can case database inconsistency, out of sync Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter -
v1.4.0-rc.11
v1.4.0-rc.11 This is a release candidate for the v1.4.0 minor release. Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 - #6304: Syncing issues, database missing sequence entries - #6335: Crash or hard shutdown can case database inconsistency, out of sync Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter -
v1.4.0-rc.10.1
v1.4.0-rc.10 This is a release candidate for the v1.4.0 minor release. Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 - #6304: Syncing issues, database missing sequence entries - #6335: Crash or hard shutdown can case database inconsistency, out of sync Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter -
v1.4.0-rc.10
v1.4.0-rc.10 This is a release candidate for the v1.4.0 minor release. Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 - #6304: Syncing issues, database missing sequence entries - #6335: Crash or hard shutdown can case database inconsistency, out of sync Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter -
v1.4.0-rc.9
v1.4.0-rc.9 This is a release candidate for the v1.4.0 minor release. Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 - #6304: Syncing issues, database missing sequence entries - #6335: Crash or hard shutdown can case database inconsistency, out of sync Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter -
v1.4.0-rc.8
v1.4.0-rc.8 This is a release candidate for the v1.4.0 minor release. Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 - #6304: Syncing issues, database missing sequence entries - #6335: Crash or hard shutdown can case database inconsistency, out of sync Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter -
v1.4.0-rc.7
v1.4.0-rc.7 This is a release candidate for the v1.4.0 minor release. Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6289: "general SOCKS server failure" since syncthing 1.3.3 - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 - #6304: Syncing issues, database missing sequence entries - #6335: Crash or hard shutdown can case database inconsistency, out of sync Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter -
v1.4.0-rc.6
v1.4.0-rc.6 This is a release candidate for the v1.4.0 minor release. Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6289: "general SOCKS server failure" since syncthing 1.3.3 - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 - #6304: Syncing issues, database missing sequence entries - #6335: Crash or hard shutdown can case database inconsistency, out of sync Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter -
v1.4.0-rc.5
v1.4.0-rc.5 This is a release candidate for the v1.4.0 minor release. Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6289: "general SOCKS server failure" since syncthing 1.3.3 - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 - #6335: Crash or hard shutdown can case database inconsistency, out of sync Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter -
v1.4.0-rc.4
v1.4.0-rc.4 This is a release candidate for the v1.4.0 minor release. Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6289: "general SOCKS server failure" since syncthing 1.3.3 - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 - #6335: Crash or hard shutdown can case database inconsistency, out of sync Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter -
v1.4.0-rc.3
v1.4.0-rc.3 This is a release candidate for the v1.4.0 minor release. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6289: "general SOCKS server failure" since syncthing 1.3.3 - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. -
v1.4.0-rc.2
v1.4.0-rc.2 This is a release candidate for the v1.4.0 minor release. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6289: "general SOCKS server failure" since syncthing 1.3.3 - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. -
v1.4.0-rc.1
v1.4.0-rc.1 This is a release candidate for the v1.4.0 minor release. Bugfixes: - #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux) - #5952: panic: Should never get a deleted file as needed when we don't have it - #6281: Progress emitter uses 100% CPU - #6289: "general SOCKS server failure" since syncthing 1.3.3 - #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0 Enhancements: - #5786: Consider always running the monitor process - #5898: Database performance: reduce duplication - #5914: Limit folder concurrency to improve performance - #6302: Avoid thundering herd issue by global request limiter Important changes: - A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. The default is 256 MiB. - The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. In addition to just limiting concurrent scans it now also limits concurrent sync operations. The default is the number of available CPU threads ("GOMAXPROCS"). - Syncthing now always runs the monitor process, which previously was disabled with -no-restart. This facilitates crash reporting and makes logging behave more consistently. The observed behavior with -no-restart should be the same as before but the internals differ. - The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade. -
v1.3.4
v1.3.4 This is a regularly scheduled patch release. Bugfixes: - #4570: Negative percentage and data to sync - #5867: Progress bar not visible - #6044: Clicking "Save" in options says "You have unsaved changes" when changing automatic upgrade setting - #6213: Tone down STUN logging a bit - #6222: Connection Error on Listing More Locally Changed Files - #6234: Docker image uses wrong path for default folder - #6240: GUI: ignore patterns path is one row too low - #6263: Panics due to database being closed
-
-
v1.3.4-rc.1
v1.3.4-rc.1 This is a release candidate for the v1.3.4 patch release. Bugfixes: - #4570: Negative percentage and data to sync - #5867: Progress bar not visible - #6044: Clicking "Save" in options says "You have unsaved changes" when changing automatic upgrade setting - #6213: Tone down STUN logging a bit - #6222: Connection Error on Listing More Locally Changed Files - #6234: Docker image uses wrong path for default folder - #6240: GUI: ignore patterns path is one row too low - #6263: Panics due to database being closed