# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1587475340 -7200
# Node ID 0fb9369e893e08cf91b3236ed61a7cd39d7f9ca6
# Parent  4bc6bcd83ae56f170dd545770a86c59c98d8f3f6
Orthanc 1.6.1

diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/developers/creating-plugins.rst
--- a/Sphinx/source/developers/creating-plugins.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/developers/creating-plugins.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -78,7 +78,7 @@
 that is part of the Orthanc source distribution:
 
 * `Plugins/Include/orthanc/OrthancCPlugin.h
-  <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/Plugins/Include/orthanc/OrthancCPlugin.h>`__
+  <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.1/Plugins/Include/orthanc/OrthancCPlugin.h>`__
 
 `Online documentation <https://sdk.orthanc-server.com/>`__ for this C
 header is available, as generated by `Doxygen
@@ -92,8 +92,8 @@
 ``HAS_ORTHANC_EXCEPTION`` is set to ``0``:
 
 * `Plugins/Samples/Common/OrthanPluginCppWrapper.h
-  <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/Plugins/Samples/Common/OrthancPluginCppWrapper.h>`__
+  <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.1/Plugins/Samples/Common/OrthancPluginCppWrapper.h>`__
 * `Plugins/Samples/Common/OrthanPluginCppWrapper.cpp
-  <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/Plugins/Samples/Common/OrthancPluginCppWrapper.cpp>`__
+  <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.1/Plugins/Samples/Common/OrthancPluginCppWrapper.cpp>`__
 * `Plugins/Samples/Common/OrthanPluginException.h
-  <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/Plugins/Samples/Common/OrthancPluginException.h>`__
+  <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.1/Plugins/Samples/Common/OrthancPluginException.h>`__
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/developers/db-versioning.rst
--- a/Sphinx/source/developers/db-versioning.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/developers/db-versioning.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -26,7 +26,7 @@
 Version                           DB v2   DB v3   DB v4   DB v5   DB v6
 ===============================   =====   =====   =====   =====   =====
 Mainline                                  u       u       u       x
-Orthanc 0.9.5 - Orthanc 1.6.0             u       u       u       x
+Orthanc 0.9.5 - Orthanc 1.6.1             u       u       u       x
 Orthanc 0.8.5 - Orthanc 0.9.4             u       u       x
 Orthanc 0.7.3 - Orthanc 0.8.4             u       x
 Orthanc 0.4.0 - Orthanc 0.7.2             x
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/faq/crash.rst
--- a/Sphinx/source/faq/crash.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/faq/crash.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -64,13 +64,13 @@
 above <segfault-plugin>` is available as the ``crash.cpp`` file, here
 is a sample debug session::
 
-  $ wget https://lsb.orthanc-server.com/orthanc/debug/1.6.0/Orthanc
+  $ wget https://lsb.orthanc-server.com/orthanc/debug/1.6.1/Orthanc
   $ chmod +x ./Orthanc
   $ gcc -fPIC -shared ./crash.cpp -I ~/orthanc/Plugins/Include -o crash.so
   $ ulimit -c unlimited
   $ echo '{ "Plugins" : ["crash.so"] }' > Configuration.json
   $ rm -f core ; ./Orthanc Configuration.json
-  W0427 15:43:24.215783 main.cpp:1436] Orthanc version: 1.6.0
+  W0427 15:43:24.215783 main.cpp:1436] Orthanc version: 1.6.1
   W0427 15:43:24.215910 main.cpp:1279] Performance warning: Non-release build, runtime debug assertions are turned on
   W0427 15:43:24.217585 OrthancConfiguration.cpp:61] Reading the configuration from: "Configuration.json"
   W0427 15:43:24.254733 main.cpp:700] Loading plugin(s) from: crash.so
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/faq/debugging.rst
--- a/Sphinx/source/faq/debugging.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/faq/debugging.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -45,13 +45,13 @@
 to debug Orthanc without compiling from sources. Here is a sample
 debug session::
 
-  $ wget https://lsb.orthanc-server.com/orthanc/debug/1.6.0/Orthanc
+  $ wget https://lsb.orthanc-server.com/orthanc/debug/1.6.1/Orthanc
   $ chmod +x ./Orthanc
   $ gdb ./Orthanc Configuration.json
   (gdb) catch throw
   Catchpoint 1 (throw)
   (gdb) run
-  W0513 15:24:42.374349 main.cpp:1436] Orthanc version: 1.6.0
+  W0513 15:24:42.374349 main.cpp:1436] Orthanc version: 1.6.1
   ---> Reproduce your error case <---
   Thread 15 "Orthanc" hit Catchpoint 1 (exception thrown), 0x00007ffff6de68bd in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   (gdb) backtrace
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/faq/dicom.rst
--- a/Sphinx/source/faq/dicom.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/faq/dicom.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -12,7 +12,7 @@
 * Turn off all the firewalls on the two computers (especially on Microsoft Windows).
 * Make sure the remote computer has `DICOM TLS encryption
   <https://www.dicomstandard.org/using/security/>`__ turned off (this
-  feature is not supported yet as of Orthanc 1.6.0).
+  feature is not supported yet as of Orthanc 1.6.1).
 * Write down on a paper the following information about each modality:
 
   * its IP address (avoid using symbolic names if possible to troubleshot any DNS problem),
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/faq/log.rst
--- a/Sphinx/source/faq/log.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/faq/log.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -49,7 +49,7 @@
 2. Stop the Orthanc service. The actual process depends on your
    version of Windows.
 
-3. Copy the just-downloaded ``Orthanc-1.6.0-Release.exe`` together
+3. Copy the just-downloaded ``Orthanc-1.6.1-Release.exe`` together
    with your configuration file (that is by default located in
    ``C:\Orthanc\Configuration.json``) into the same folder
    (e.g. ``C:\Temp``).
@@ -58,7 +58,7 @@
    ``Orthanc.log`` file::
 
    $ cd C:\Temp
-   $ Orthanc-1.6.0-Release.exe --verbose Configuration.json > Orthanc.log 2<&1
+   $ Orthanc-1.6.1-Release.exe --verbose Configuration.json > Orthanc.log 2<&1
 
 5. Once the log has been generated (by default, it is available as
    ``C:\Temp\Orthanc.log``), stop Orthanc and possibly restart the
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/faq/orthanc-storage.rst
--- a/Sphinx/source/faq/orthanc-storage.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/faq/orthanc-storage.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -59,9 +59,9 @@
 database schema is kept as simple as possible, and can be found in the
 following two files of the source code of Orthanc:
 `PrepareDatabase.sql
-<https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/OrthancServer/Database/PrepareDatabase.sql>`__
+<https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.1/OrthancServer/Database/PrepareDatabase.sql>`__
 and `InstallTrackAttachmentsSize.sql
-<https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/OrthancServer/Database/InstallTrackAttachmentsSize.sql>`__.
+<https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.1/OrthancServer/Database/InstallTrackAttachmentsSize.sql>`__.
 
 
 Direct access
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/faq/scalability.rst
--- a/Sphinx/source/faq/scalability.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/faq/scalability.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -54,7 +54,7 @@
 Here is a generic setup that should provide best performance in the
 presence of large databases:
 
-* Make sure to use the latest release of Orthanc (1.6.0 at the time of
+* Make sure to use the latest release of Orthanc (1.6.1 at the time of
   writing).
 
 * We suggest to use the latest release of the :ref:`PostgreSQL plugin
@@ -134,9 +134,9 @@
 arenas <https://sourceware.org/glibc/wiki/MallocInternals>`__ are
 created by the glibc standard library (up to one per thread). As a
 consequence, if each one of the 50 threads in the HTTP server of
-Orthanc (this was the default value in Orthanc <= 1.6.0) allocates at
-some point, say, 50MB, the total memory usage reported as "VmRSS" can
-grow up to 50 threads x 50MB = 2.5GB, even if the Orthanc threads
+Orthanc (default value of the ``HttpThreadsCount`` option) allocates
+at some point, say, 50MB, the total memory usage reported as "VmRSS"
+can grow up to 50 threads x 50MB = 2.5GB, even if the Orthanc threads
 properly free all the buffers.
 
 .. highlight:: bash
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/faq/security.rst
--- a/Sphinx/source/faq/security.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/faq/security.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -187,7 +187,7 @@
   configuration of remote modalities.
   
 
-**Remark:** As of Orthanc 1.6.0, `DICOM TLS encryption
+**Remark:** As of Orthanc 1.6.1, `DICOM TLS encryption
 <https://www.dicomstandard.org/using/security/>`__ is not supported
 yet. We are looking for :ref:`an industrial sponsor <contributing>` to
 get this feature implemented, as it is useful in enterprise and cloud
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/faq/transcoding.rst
--- a/Sphinx/source/faq/transcoding.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/faq/transcoding.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -6,7 +6,7 @@
 General information
 -------------------
 
-As of release 1.6.0, Orthanc does not feature support for transcoding
+As of release 1.6.1, Orthanc does not feature support for transcoding
 DICOM instances yet. In other words, the Orthanc core never changes
 the :ref:`transfer syntax <dicom-pixel-data>` of some DICOM instance
 when it has to send it to another modality using the DICOM protocol.
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/plugins/postgresql.rst
--- a/Sphinx/source/plugins/postgresql.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/plugins/postgresql.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -248,7 +248,7 @@
 between several instances of Orthanc that would simultaneously write
 to the database.
 
-As a consequence, as of Orthanc 1.6.0, when connecting multiple
+As a consequence, as of Orthanc 1.6.1, when connecting multiple
 Orthanc to a single database by setting ``Lock`` to ``false``, there
 should only be one instance of Orthanc acting as a writer and all the
 other instances of Orthanc acting as readers only. Be careful to set
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/users/advanced-rest.rst
--- a/Sphinx/source/users/advanced-rest.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/users/advanced-rest.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -128,7 +128,7 @@
   ``ErrorCode`` and ``ErrorDescription`` fields for more information.
 * ``Paused``: The job has been paused.
 * ``Retry``: The job has failed internally, and has been scheduled for
-  re-submission after a delay. As of Orthanc 1.6.0, this feature is not
+  re-submission after a delay. As of Orthanc 1.6.1, this feature is not
   used by any type of job.
 
 In order to wait for the end of an asynchronous call, the caller will
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/users/configuration.rst
--- a/Sphinx/source/users/configuration.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/users/configuration.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -7,7 +7,7 @@
 Configuring Orthanc simply consists in providing a configuration file.
 Orthanc has numerous configuration that are documented in the `default
 configuration file
-<https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/Resources/Configuration.json>`_. This
+<https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.1/Resources/Configuration.json>`_. This
 file is in the `JSON <https://en.wikipedia.org/wiki/JSON>`_ file
 format. You can generate this file file with the following call::
 
diff -r 4bc6bcd83ae5 -r 0fb9369e893e Sphinx/source/users/docker.rst
--- a/Sphinx/source/users/docker.rst	Tue Apr 21 08:58:56 2020 +0200
+++ b/Sphinx/source/users/docker.rst	Tue Apr 21 15:22:20 2020 +0200
@@ -66,7 +66,7 @@
 If more stability is required, you can select the official release of
 Orthanc to be run::
 
-  $ docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc:1.6.0
+  $ docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc:1.6.1
 
 Passing additional command-line options (e.g. to make Orthanc verbose)
 can be done as follows (note the ``/etc/orthanc`` option that is
@@ -88,7 +88,7 @@
 
 Or you can also start a specific version of Orthanc for more stability::
 
-  $ docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc-plugins:1.6.0
+  $ docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc-plugins:1.6.1
 
 If you have an interest in the :ref:`Python plugin <python-plugin>`,
 you can use the ``orthanc-python`` image. The latter image is a
@@ -96,7 +96,7 @@
 Python 3.7 interpreter. Here is how to start this image::
 
   $ docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc-python
-  $ docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc-python:1.6.0
+  $ docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc-python:1.6.1
   
 
 Fine-tuning the configuration
@@ -148,7 +148,7 @@
   version: '3.1'  # Secrets are only available since this version of Docker Compose
   services:
     orthanc:
-      image: jodogne/orthanc-plugins:1.6.0
+      image: jodogne/orthanc-plugins:1.6.1
       command: /run/secrets/  # Path to the configuration files (stored as secrets)
       ports:
         - 8042:8042
@@ -186,7 +186,7 @@
 container to some path in the filesystem of your Linux host, e.g.::
 
   $ mkdir /tmp/orthanc-db
-  $ docker run -p 4242:4242 -p 8042:8042 --rm -v /tmp/orthanc-db/:/var/lib/orthanc/db/ jodogne/orthanc:1.6.0 
+  $ docker run -p 4242:4242 -p 8042:8042 --rm -v /tmp/orthanc-db/:/var/lib/orthanc/db/ jodogne/orthanc:1.6.1 
 
 
 Whole-slide imaging support
@@ -307,4 +307,4 @@
 * The build artifacts can be found in folder ``/root/orthanc/Build``.
 
 * This command launches the mainline version. To start a released version,
-  use e.g. ``jodogne/orthanc-debug:1.6.0``.
+  use e.g. ``jodogne/orthanc-debug:1.6.1``.