Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-7113

NPE when adding a changest to a review with no commit message from a SVN Repo

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • 3.9.0
    • 3.6.2
    • None

      When adding a changeset to a review, if the changeset has no commit message then a NullPointerException is received;

      Steps to reproduce;

      1. Perform a commit without a message
      2. Create a Review
      3. Try to add the changeset that contains no commit message
      4. NullPointerException error retrieved.

      Tested and confirmed with subversion.

      The workaround is simply to add a message when performing the commit.

        1. Screen Shot 2015-02-03 at 14.35.39.png
          Screen Shot 2015-02-03 at 14.35.39.png
          169 kB

            [CRUC-7113] NPE when adding a changest to a review with no commit message from a SVN Repo

            David Lahn (Inactive) added a comment -

            This is fixed in CRUC-7259.

            Another workaround is to set a review title before adding the changeset to the review. As discussed in CRUC-7259, this happens due to an NPE while trying to extract a review title from the commit message.

            David Lahn (Inactive) added a comment - This is fixed in CRUC-7259 . Another workaround is to set a review title before adding the changeset to the review. As discussed in CRUC-7259 , this happens due to an NPE while trying to extract a review title from the commit message.

            Jay Armstrong added a comment -

            "The workaround is simply to add a message when performing the commit." That's not exactly a useful workaround for all the cases where the commit has already happened.

            Jay Armstrong added a comment - "The workaround is simply to add a message when performing the commit." That's not exactly a useful workaround for all the cases where the commit has already happened.

              Unassigned Unassigned
              chparker ♚♛♜♝♞♟♔♕♖♗♘♙ (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: