Changelog History
Page 5
-
v1.4.2-rc.1 Changes
April 07, 2020v1.4.2
⚡️ This is a tiny update to fix a couple of crashes that should not have
⬆️ landed in 1.4.1, and revert a change to the upgrade code that puts
⬆️ unnecessary load on the upgrade server.🛠 Bugfixes:
- 🔀 #6499: panic: nil pointer dereference in usage reporting
-
v1.4.1
April 06, 2020 -
v1.4.1-rc.3 Changes
March 20, 2020v1.4.1
🛠 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 Changes
March 19, 2020v1.4.1
🛠 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 Changes
March 18, 2020v1.4.1
🛠 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 Changes
March 17, 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.9 Changes
February 28, 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.8 Changes
February 27, 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.7 Changes
February 22, 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
- 🔀 #6304: Syncing issues, database missing sequence entries
- 🔀 #6335: Crash or hard shutdown can case database inconsistency, out of sync
✨ Enhancements
-
v1.4.0-rc.6
February 22, 2020