Skip to content
Snippets Groups Projects

Fixed exceptions

Merged Sanjeev-SLB requested to merge fix-tests into master

Type of change

  • Bug Fix
  • Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

  • [YES/NO] NO

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a breaking change?

  • [YES/NO] NO

What is the current behavior?

What is the new/expected behavior?

Have you added/updated Unit Tests and Integration Tests?

Any other useful information

Edited by Sanjeev-SLB

Merge request reports

Merge request pipeline #102641 passed

Pipeline: Notification

#102643

    Merge request pipeline passed for 7673dd9f

    Deployed to G‎CP‎ 3 years ago
    Deployed to A‎WS‎ 3 years ago
    Deployed to I‎BM‎ 3 years ago
    Approved by

    Merged by Sanjeev-SLBSanjeev-SLB 3 years ago (Apr 5, 2022 12:54pm UTC)

    Merge details

    • Changes merged into master with b038451f.
    • Deleted the source branch.

    Pipeline #102885 failed

    Pipeline failed for b038451f on master

    Deployed to I‎BM‎ 3 years ago
    Deployed to A‎WS‎ 3 years ago
    Deployed to G‎CP‎ 3 years ago

    Activity

    Filter activity
    • Approvals
    • Assignees & reviewers
    • Comments (from bots)
    • Comments (from users)
    • Commits & branches
    • Edits
    • Labels
    • Lock status
    • Mentions
    • Merge request status
    • Tracking
  • Sanjeev-SLB added 3 commits

    added 3 commits

    Compare with previous version

  • Sanjeev-SLB resolved all threads

    resolved all threads

  • 86 86 LOGGER.info("Message delivery status is 'Abandon' with notificationId: {}, Count: {}", notificationContent.getNotificationId(), message.getDeliveryCount());
  • 86 86 LOGGER.info("Message delivery status is 'Abandon' with notificationId: {}, Count: {}", notificationContent.getNotificationId(), message.getDeliveryCount());
    87 87 } else {
    88 88 LOGGER.error(NOT_ACKNOWLEDGE);
    89 throw new Exception(NOT_ACKNOWLEDGE);
  • Author Contributor

    @sasarava Implemented same as Notification V1, the not acknowledge events supposed to throw an error.

  • Sanjeev-SLB added 1 commit

    added 1 commit

    Compare with previous version

  • Sanjeev-SLB added 4 commits

    added 4 commits

    Compare with previous version

  • Sanjeev-SLB added 1 commit

    added 1 commit

    Compare with previous version

  • Sathyanarayanan Saravanamuthu approved this merge request

    approved this merge request

  • Sanjeev-SLB added 3 commits

    added 3 commits

    Compare with previous version

  • Sathyanarayanan Saravanamuthu approved this merge request

    approved this merge request

  • Sanjeev-SLB mentioned in commit b038451f

    mentioned in commit b038451f

  • merged

  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Please register or sign in to reply
    Loading