All Versions
86
Latest Version
Avg Release Cycle
6 days
Latest Release
1235 days ago

Changelog History
Page 6

  • v1.4.0-rc.5 Changes

    February 14, 2020

    v1.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

    • 🔀 #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 Changes

    February 13, 2020

    v1.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

    • 🔀 #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 Changes

    February 12, 2020

    v1.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

    • 🔀 #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.2 Changes

    February 11, 2020

    v1.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

    • 🔀 #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 Changes

    March 06, 2020

    v1.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:

    • 🔀 #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 Changes

    February 29, 2020

    v1.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:

    • 🔀 #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.1

    February 10, 2020

  • v1.3.4

    February 03, 2020

  • v1.3.4-rc.1 Changes

    January 14, 2020

    v1.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, 2020

    v1.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

    • ⬆️ #5887: Upgrade Button Does Not Have Confirmation Dialog
    • 🔀 #6057: "Nearby devices" links should look more like links (mouse pointer)
    • 🔀 #6190: Do not create .stignore if there are no ignore patterns