Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-2674

Exception thrown when a test scenario containing a tag is renamed without saving

XMLWordPrintable

    • Release Notes
    • CR1
    • ?
    • Hide

      The exception is thrown when doing the following:
      1. Create a Legacy Test Scenario
      2. Add a tag (Overview -> metadata)
      3. Rename the file by clicking on toolbar
      4. On rename dialog click Save and Rename
      5. See the exception in logs

      The exception is not thrown when doing the following:
      1. Create a Legacy Test Scenario
      2. Add a tag (Overview -> metadata)
      3. Save the file by clicking on toolbar
      4. Rename the file by clicking on toolbar
      5. On rename dialog click Save and Rename
      6. No exception in logs
      5. See the exception in logs

      Show
      The exception is thrown when doing the following: 1. Create a Legacy Test Scenario 2. Add a tag (Overview -> metadata) 3. Rename the file by clicking on toolbar 4. On rename dialog click Save and Rename 5. See the exception in logs The exception is not thrown when doing the following: 1. Create a Legacy Test Scenario 2. Add a tag (Overview -> metadata) 3. Save the file by clicking on toolbar 4. Rename the file by clicking on toolbar 5. On rename dialog click Save and Rename 6. No exception in logs 5. See the exception in logs
    • 2020 Week 16-18 (from Apr 13)

      When we create a test scenario in business central 7.6. and then we add a tag to it (overview -> metadata -> tags -> add new tag -> Rename -> Save and Rename) an exception is thrown which can be seen in the logs. However, The exception is not thrown if the asset is saved first before renaming it (overview -> metadata -> tags -> add new tag -> save -> rename -> Save and Rename

      9:47:28,504 ERROR [org.uberfire.java.nio.fs.jgit.util.GitImpl] (EJB default - 2) Unexpected exception (1/0).: org.uberfire.java.nio.file.NoSuchFileException
      at deployment.business-central.war//org.uberfire.java.nio.fs.jgit.util.commands.BlobAsInputStream.execute(BlobAsInputStream.java:66)
      at deployment.business-central.war//org.uberfire.java.nio.fs.jgit.util.GitImpl.lambda$blobAsInputStream$2(GitImpl.java:341)
      at deployment.business-central.war//org.uberfire.java.nio.fs.jgit.util.GitImpl.retryIfNeeded(GitImpl.java:473)
      at deployment.business-central.war//org.uberfire.java.nio.fs.jgit.util.GitImpl.blobAsInputStream(GitImpl.java:338)
      at deployment.business-central.war//org.uberfire.java.nio.fs.jgit.JGitFileSystemProvider.newInputStream(JGitFileSystemProvider.java:1049)
      at deployment.business-central.war//org.uberfire.java.nio.file.Files.newInputStream(Files.java:100)

      See attached file for stacktrace

        1. RHPAM-2308-stacktrace.txt
          71 kB

              r_anand Rishiraj Anand
              r_anand Rishiraj Anand
              Barbora Kapustova Barbora Kapustova
              Barbora Kapustova Barbora Kapustova
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: