Mercurial > hg > orthanc
comparison NEWS @ 5605:3f24eb4013d8 find-refactoring
integration mainline->find-refactoring
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Wed, 08 May 2024 10:30:57 +0200 |
parents | aafe402ec950 c2a2fb8e868d |
children | f1ce8dd361b7 |
comparison
equal
deleted
inserted
replaced
5602:e4e7ca3d206e | 5605:3f24eb4013d8 |
---|---|
1 Pending changes in the mainline | 1 Pending changes in the mainline |
2 =============================== | 2 =============================== |
3 | |
4 Maintenance | |
5 ----------- | |
6 | |
7 * In C-Find queries including GenericGroupLength tags, Orthanc was still | |
8 extracting these tags from the storage although they were already ignored | |
9 and not returned in the response. | |
10 They are now removed from the query earlier to avoid this disk access that | |
11 could slow down the response time. Note that this seems to happen mainly | |
12 when the query originates from some GE devices (AWS). | |
13 * The 0x0111 DIMSE Status is now considered as a warning instead of an error | |
14 when received as a response to a C-Store. | |
15 See https://discourse.orthanc-server.org/t/ignore-dimse-status-0x0111-when-sending-partial-duplicate-studies/4555/3 | |
16 * Removed potential PHI from the logs when Orthanc encounters an error while | |
17 creating a zip file. | |
18 | |
19 Bug Fixes | |
20 --------- | |
21 | |
22 * When working with "DicomTlsEnabled": true and "DicomTlsRemoteCertificateRequired": false, | |
23 Orthanc was refusing to start if no "DicomTlsTrustedCertificates" was provided. | |
24 | |
25 | 3 |
26 REST API | 4 REST API |
27 -------- | 5 -------- |
28 | 6 |
29 * API version upgraded to 24 | 7 * API version upgraded to 24 |
46 plugins to log messages. This new primitive will display the plugin | 24 plugins to log messages. This new primitive will display the plugin |
47 name, the plugin file name, and the plugin line number in the | 25 name, the plugin file name, and the plugin line number in the |
48 logs. If they are not using the LOG() facilities provided by the | 26 logs. If they are not using the LOG() facilities provided by the |
49 OrthancFramework, plugins should now use ORTHANC_PLUGINS_LOG_INFO(), | 27 OrthancFramework, plugins should now use ORTHANC_PLUGINS_LOG_INFO(), |
50 ORTHANC_PLUGINS_LOG_WARNING(), and ORTHANC_PLUGINS_LOG_ERROR(). | 28 ORTHANC_PLUGINS_LOG_WARNING(), and ORTHANC_PLUGINS_LOG_ERROR(). |
29 | |
30 Maintenance | |
31 ----------- | |
32 | |
33 * In C-Find queries including GenericGroupLength tags, Orthanc was still | |
34 extracting these tags from the storage although they were already ignored | |
35 and not returned in the response. | |
36 They are now removed from the query earlier to avoid this disk access that | |
37 could slow down the response time. Note that this seems to happen mainly | |
38 when the query originates from some GE devices (AWS). | |
39 * The 0x0111 DIMSE Status is now considered as a warning instead of an error | |
40 when received as a response to a C-Store. | |
41 See https://discourse.orthanc-server.org/t/ignore-dimse-status-0x0111-when-sending-partial-duplicate-studies/4555/3 | |
42 * Removed potential PHI from the logs when Orthanc encounters an error while | |
43 creating a zip file. | |
44 * Monitoring of stable resources now also takes into consideration the | |
45 resource type, not only the resource identifier identifier. | |
46 * When working with "DicomTlsEnabled": true and "DicomTlsRemoteCertificateRequired": false, | |
47 Orthanc was refusing to start if no "DicomTlsTrustedCertificates" was provided. | |
51 | 48 |
52 | 49 |
53 Version 1.12.3 (2024-01-31) | 50 Version 1.12.3 (2024-01-31) |
54 =========================== | 51 =========================== |
55 | 52 |