syncthing 标签 - Gitee.com

v1.6.0-rc.5

This release performs a database schema migration, and adds the
`BlockPullOrder`, `DisableFsync` and `MaxConcurrentWrites` folder
options to the configuration schema.

The `LocalChangeDetected` event no longer has the `action` set to
`added` for new files, instead showing `modified` for all local file
changes.

Bugfixes:

- #3876: Removing and re-adding a folder may cause data loss
- #5731: 100% CPU every minute on watch setup retry
- #6268: Out of sync panel layout overflows
- #6557: Folder error repeatedly set and unset
- #6559: Deadlock on folder unsubscribe
- #6576: Versioning params in config flip flop in order
- #6578: Allow rescan at folder state "Local Additions"
- #6583: Distributed deadlock on request
- #6604: Docker healthcheck fails when run in host network

Enhancements:

- #5224: Accept new connections in place of old ones when appropriate
- #6530: Add "Pause All"/"Resume All" button for devices
- #6541: Limit number of concurrent writes while syncing

Other issues:

- #6575: Incomprehensible error message: 'directory is not empty; files within are probably ignored on connected devices only'
- #6584: A field in a structure is sometimes protected by Mutex, but sometimes unprotected.

8c74177

2020-05-20 17:01

下载

v1.6.0-rc.4

This release performs a database schema migration, and adds the
`BlockPullOrder`, `DisableFsync` and `MaxConcurrentWrites` folder
options to the configuration schema.

The `LocalChangeDetected` event no longer has the `action` set to
`added` for new files, instead showing `modified` for all local file
changes.

Bugfixes:

- #3876: Removing and re-adding a folder may cause data loss
- #5731: 100% CPU every minute on watch setup retry
- #6268: Out of sync panel layout overflows
- #6557: Folder error repeatedly set and unset
- #6559: Deadlock on folder unsubscribe
- #6576: Versioning params in config flip flop in order
- #6578: Allow rescan at folder state "Local Additions"
- #6583: Distributed deadlock on request
- #6604: Docker healthcheck fails when run in host network

Enhancements:

- #5224: Accept new connections in place of old ones when appropriate
- #6530: Add "Pause All"/"Resume All" button for devices
- #6541: Limit number of concurrent writes while syncing

Other issues:

- #6575: Incomprehensible error message: 'directory is not empty; files within are probably ignored on connected devices only'
- #6584: A field in a structure is sometimes protected by Mutex, but sometimes unprotected.

22c222b

2020-05-17 05:05

下载

v1.6.0-rc.3

This release performs a database schema migration, and adds the
`BlockPullOrder`, `DisableFsync` and `MaxConcurrentWrites` folder
options to the configuration schema.

The `LocalChangeDetected` event no longer has the `action` set to
`added` for new files, instead showing `modified` for all local file
changes.

Bugfixes:

- #3876: Removing and re-adding a folder may cause data loss
- #5731: 100% CPU every minute on watch setup retry
- #6268: Out of sync panel layout overflows
- #6557: Folder error repeatedly set and unset
- #6559: Deadlock on folder unsubscribe
- #6576: Versioning params in config flip flop in order
- #6578: Allow rescan at folder state "Local Additions"
- #6583: Distributed deadlock on request
- #6604: Docker healthcheck fails when run in host network

Enhancements:

- #5224: Accept new connections in place of old ones when appropriate
- #6530: Add "Pause All"/"Resume All" button for devices
- #6541: Limit number of concurrent writes while syncing

Other issues:

- #6575: Incomprehensible error message: 'directory is not empty; files within are probably ignored on connected devices only'
- #6584: A field in a structure is sometimes protected by Mutex, but sometimes unprotected.

258341f

2020-05-16 20:39

下载

v1.6.0-rc.2

This release performs a database schema migration, and adds the
`BlockPullOrder`, `DisableFsync` and `MaxConcurrentWrites` folder
options to the configuration schema.

The `LocalChangeDetected` event no longer has the `action` set to
`added` for new files, instead showing `modified` for all local file
changes.

Bugfixes:

- #3876: Removing and re-adding a folder may cause data loss
- #5731: 100% CPU every minute on watch setup retry
- #6268: Out of sync panel layout overflows
- #6557: Folder error repeatedly set and unset
- #6559: Deadlock on folder unsubscribe
- #6576: Versioning params in config flip flop in order
- #6578: Allow rescan at folder state "Local Additions"
- #6583: Distributed deadlock on request
- #6604: Docker healthcheck fails when run in host network

Enhancements:

- #5224: Accept new connections in place of old ones when appropriate
- #6530: Add "Pause All"/"Resume All" button for devices
- #6541: Limit number of concurrent writes while syncing

Other issues:

- #6575: Incomprehensible error message: 'directory is not empty; files within are probably ignored on connected devices only'
- #6584: A field in a structure is sometimes protected by Mutex, but sometimes unprotected.

6768dae

2020-05-14 02:38

下载

v1.6.0-rc.1

This release performs a database schema migration, and adds the
`BlockPullOrder`, `DisableFsync` and `MaxConcurrentWrites folder
options to the configuration schema.

The `LocalChangeDetected` event no longer has the `action` set to
`added` for new files, instead showing `modified` for all local file
changes.

Bugfixes:

- #3876: Removing and re-adding a folder may cause data loss
- #5731: 100% CPU every minute on watch setup retry
- #6268: Out of sync panel layout overflows
- #6557: Folder error repeatedly set and unset
- #6559: Deadlock on folder unsubscribe
- #6576: Versioning params in config flip flop in order
- #6578: Allow rescan at folder state "Local Additions"
- #6583: Distributed deadlock on request
- #6604: Docker healthcheck fails when run in host network

Enhancements:

- #5224: Accept new connections in place of old ones when appropriate
- #6530: Add "Pause All"/"Resume All" button for devices
- #6541: Limit number of concurrent writes while syncing

Other issues:

- #6575: Incomprehensible error message: 'directory is not empty; files within are probably ignored on connected devices only'
- #6584: A field in a structure is sometimes protected by Mutex, but sometimes unprotected.

6201eeb

2020-05-12 05:44

下载

v1.5.0

This release changes the default location for the index database under
some circumstances. Two new flags can also be used to affect the
location of the configuration (`-config`) and database (`-data`)
separately. The old `-home` flag is equivalent to setting both of these
to the same directory. When no flags are given the following logic is
used to determine the data location:

- If a database exists in the old default location, that location is
  still used. This means existing installations are not affected by this
  change.
- If `$XDG_DATA_HOME` is set, use `$XDG_DATA_HOME/syncthing`.
- If `~/.local/share/syncthing` exists, use that location.
- Use the old default location.

This logic is used on non-Windows, non-Mac platforms only. On Windows
and Mac the logic is unchanged.

Bugfixes:

- #3808: gui: Number of days must be number flashes red then disappears
- #5809: stdiscosrv failed to load keypair without proper error message
- #6410: Wrong 30-days-interval in staggered versioning
- #6430: Incorrect out-of-sync/locally changed status indication on folders
- #6436: Revert Local Changes red button does not work correctly
- #6440: Doesn't run monitor process when started with STNORESTART=1
- #6450: LDAP auth doesn't handle LDAPS with certificate validation
- #6487: Scan problem within single unignored subdirectory prevents bidirectional sync

Enhancements:

- #4924: Move index db to $XDG_DATA_HOME/syncthing/
- #5376: Improve LDAP authentication
- #6384: Do auto upgrades early and synchronously on startup
- #6416: Improve device status for "unused" devices
- #6432: Deleted file that existed locally only reported as locally changed
- #6437: Don't start browser when restarting after upgrade

Other issues:

- #6471: Windows exe isn't properly version tagged

ebad9e2

2020-04-22 04:42

下载

v1.5.0-rc.2

This release changes the default location for the index database under
some circumstances. Two new flags can also be used to affect the
location of the configuration (`-config`) and database (`-data`)
separately. The old `-home` flag is equivalent to setting both of these
to the same directory. When no flags are given the following logic is
used to determine the data location:

- If a database exists in the old default location, that location is
  still used. This means existing installations are not affected by this
  change.
- If `$XDG_DATA_HOME` is set, use `$XDG_DATA_HOME/syncthing`.
- If `~/.local/share/syncthing` exists, use that location.
- Use the old default location.

This logic is used on non-Windows, non-Mac platforms only. On Windows
and Mac the logic is unchanged.

Bugfixes:

- #3808: gui: Number of days must be number flashes red then disappears
- #5809: stdiscosrv failed to load keypair without proper error message
- #6410: Wrong 30-days-interval in staggered versioning
- #6430: Incorrect out-of-sync/locally changed status indication on folders
- #6436: Revert Local Changes red button does not work correctly
- #6440: Doesn't run monitor process when started with STNORESTART=1
- #6450: LDAP auth doesn't handle LDAPS with certificate validation
- #6487: Scan problem within single unignored subdirectory prevents bidirectional sync

Enhancements:

- #4924: Move index db to $XDG_DATA_HOME/syncthing/
- #5376: Improve LDAP authentication
- #6384: Do auto upgrades early and synchronously on startup
- #6416: Improve device status for "unused" devices
- #6432: Deleted file that existed locally only reported as locally changed
- #6437: Don't start browser when restarting after upgrade

Other issues:

- #6471: Windows exe isn't properly version tagged

ebad9e2

2020-04-22 04:42

下载

v1.5.0-rc.1

v1.5.0

This release changes the default location for the index database under
some circumstances. Two new flags can also be used to affect the
location of the configuration (`-config`) and database (`-data`)
separately. The old `-home` flag is equivalent to setting both of these
to the same directory. When no flags are given the following logic is
used to determine the data location:

- If a database exists in the old default location, that location is
  still used. This means existing installations are not affected by this
  change.
- If `$XDG_DATA_HOME` is set, use `$XDG_DATA_HOME/syncthing`.
- If `~/.local/share/syncthing` exists, use that location.
- Use the old default location.

This logic is used on non-Windows, non-Mac platforms only. On Windows
and Mac the logic is unchanged.

Bugfixes:

- #3808: gui: Number of days must be number flashes red then disappears
- #5809: stdiscosrv failed to load keypair without proper error message
- #6410: Wrong 30-days-interval in staggered versioning
- #6430: Incorrect out-of-sync/locally changed status indication on folders
- #6436: Revert Local Changes red button does not work correctly
- #6440: Doesn't run monitor process when started with STNORESTART=1
- #6450: LDAP auth doesn't handle LDAPS with certificate validation
- #6487: Scan problem within single unignored subdirectory prevents bidirectional sync

Enhancements:

- #4924: Move index db to $XDG_DATA_HOME/syncthing/
- #5376: Improve LDAP authentication
- #6384: Do auto upgrades early and synchronously on startup
- #6416: Improve device status for "unused" devices
- #6432: Deleted file that existed locally only reported as locally changed
- #6437: Don't start browser when restarting after upgrade

Other issues:

- #6471: Windows exe isn't properly version tagged

ab92f85

2020-04-13 16:21

下载

v1.4.2

0f532a5

2020-04-07 19:13

下载

v1.4.2-rc.1

0f532a5

2020-04-07 19:13

下载

v1.4.1

f1b253f

2020-03-20 19:07

下载

v1.4.1-rc.3

f1b253f

2020-03-20 19:07

下载

v1.4.1-rc.2

b33d5e5

2020-03-19 22:58

下载

v1.4.1-rc.1

00b2340

2020-03-19 03:33

下载

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

db02545

2020-03-07 03:50

下载

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

db02545

2020-03-07 03:50

下载

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

52e72e0

2020-03-01 02:51

下载

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

52e72e0

2020-03-01 02:51

下载

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

0b61001

2020-02-28 18:16

下载

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

9a1df97

2020-02-27 18:21

下载

bhg1410/syncthing .gitee-modal { width: 500px !important; }

搜索帮助

bhg1410/syncthing