Uploaded image for project: 'PROFINET Core'
  1. PROFINET Core
  2. PSPNCORE-313

Sort algorithm for expected submodules not working as expected

          Details

          • Type: Bug
          • Status: Closed
          • Priority: Minor
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: V1.8.0.3, V1.9.0.0
          • Component/s: Device
          • Labels:
          • Account:
            SPC Profinet Core (SPCPROFINET)

            Description

            The sorting algorithm for expected submodules is not working properly. This causes unexpected behavior in case of unsorted Expected Submodule Blocks in connect requests. E.g. Invalid ModuleDiff blocks and wrong or missing check indications.

            The problem is most likely seen, but not limited to configurations with multiple APIs.

              Attachments

                Issue Links

                blocks

                Change - PSPNSV5-90 Upgrade Profinet Core to V1.8.0.3

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Closed
                is blocked by

                Bug - A problem which impairs or prevents the functions of the product. PSPNSV4-1111 Invalid Module Diff Block and Check Indications with unsorted Expected submodule blocks

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. PSPNSV5-99 Invalid Module Diff Block and Check Indications with unsorted Expected submodule blocks

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Closed
                relates to

                Bug - A problem which impairs or prevents the functions of the product. PSPNCORE-420 Receiving an unsorted expected submodule list within connect.req leads to unexpected ModuleDiffBlock

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Closed

                  Expenses

                    Activity

                      Status Description

                        People

                        • Reporter:
                          AMesser Andreas Messer
                        • Votes:
                          0 Vote for this issue
                          Watchers:
                          0 Start watching this issue

                          Dates

                          • Created:
                            Updated:
                            Resolved: