[EXTDAM-196] S3 IndexOutOfBoundsException occurs Created: 19/Nov/20  Updated: 01/Dec/20  Resolved: 30/Nov/20

Status: Closed
Project: External DAMs
Component/s: None
Affects Version/s: 1.0.2
Fix Version/s: 1.0.3

Type: Bug Priority: Neutral
Reporter: Julie Legendre Assignee: Rishab Dhar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2020-11-19-13-04-55-582.png     Text File second pb.txt    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Documentation update required:
Yes
Date of First Response:
Epic Link: DAM Phase 2
Sprint: Add-Ons 52
Story Points: 1

 Description   

Bundle installed today (v1.0.2)

  1. Set S3 pageSize property to 2 (unsure if this is related - removed property and tried again with the same result).
  2. Click on any S3 asset and an error appears:

    Stack trace attached.

Solution

  • pageSize set minimum to 100


 Comments   
Comment by Rishab Dhar [ 30/Nov/20 ]

pageSize property validation checks introduced (value below 100 are ignored, with a warning message).

Generated at Mon Feb 12 01:52:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.