syncthing 标签 - Gitee.com

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

a5e12a0

2020-02-23 00:44

下载

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

0fb2cd5

2020-02-22 16:36

下载

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

bb375b1

2020-02-14 15:11

下载

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

71de6fe

2020-02-13 22:39

下载

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.

d95a087

2020-02-12 19:00

下载

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.

04e648f

2020-02-11 22:37

下载

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.

b61da48

2020-02-10 17:48

下载

v1.3.4

a79de84

2020-01-14 15:01

下载

v1.0.1-cs.1

897f238

2019-07-27 04:18

下载