Changelog History
Page 6
-
v1.4.0-rc.5 Changes
February 14, 2020v1.4.0
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
0๏ธโฃ 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
0๏ธโฃ 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
-
v1.4.0-rc.4 Changes
February 13, 2020v1.4.0
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
0๏ธโฃ 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
0๏ธโฃ 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
-
v1.4.0-rc.3 Changes
February 12, 2020v1.4.0
๐ 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
-
v1.4.0-rc.2 Changes
February 11, 2020v1.4.0
๐ 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
-
v1.4.0-rc.11 Changes
March 06, 2020v1.4.0
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
0๏ธโฃ 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
0๏ธโฃ 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:
-
v1.4.0-rc.10 Changes
February 29, 2020v1.4.0
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
0๏ธโฃ 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
0๏ธโฃ 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:
-
v1.4.0-rc.1
February 10, 2020 -
v1.3.4
February 03, 2020 -
v1.3.4-rc.1 Changes
January 14, 2020v1.3.4
๐ 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.3 Changes
January 07, 2020v1.3.3
๐ Bugfixes
- ๐ #6104: Windows: Syncthing log file filling up primary drive.
- ๐ #6133: Race condition in restarting folder
- ๐ #6139: Some sync errors get cleared despite them still being valid
- ๐ #6206: Soft limit for maxfiles is NOT increased to the hard one on macOS
โจ Enhancements