[MGNLUI-8242] Failing app definition resolution prevents startup of webapp Created: 28/Jul/23  Updated: 09/Oct/23  Resolved: 09/Oct/23

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Adrian Brooks Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stacktrace-1.txt    
Issue Links:
duplicate
duplicates MGNLUI-8237 Subscription goes into error when add... Closed
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
Team: Nucleus

 Description   

Steps to reproduce

  1.  Add the module attached to the light-modules folder in my Git repo connected to this subscription (ryiaaa9x3yojqj0e), at some point later the subscription goes into error.
  2.  See also this discussion thread on slack

.. Logs, screenshots, gifs...

Expected results

  1. Error resilience in this case, so that the webapp can start-up even if a decoration is set improperly
  2. Clarify which decorations are allowed on 6.3/SaaS (SAAS-267)

.. Justify non-trivial expectations with a link to a doc or a relevant discussion.

Actual results

Subscription goes into an error state at some point after the decoration is added (not immediately). It happened to me already on three separate subscriptions: adrian.brooks+docu@magnolia-cms.com, adrian.brooks+july2023@magnolia-cms.com, and adrian.brooks+reborn@magnolia-cms.com

Workaround

Development notes



 Comments   
Comment by Adrian Brooks [ 09/Oct/23 ]

Moved to the other board (SaaS related): https://magnolia-cms.atlassian.net/browse/MX-776

Generated at Mon Feb 12 09:53:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.