[ 
https://issues.apache.org/jira/browse/IGNITE-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilya Borisov updated IGNITE-10726:
----------------------------------
    Description: 
*What happens:*
AngularJS error is thrown when switching between configuration domain models.

*How to reproduce:*
1. Start demo mode, launch web agent.
2. Go to configuration and perform DB import once.
3. Open the result configuration domain models section.
4. Import from in place DB, choose to overwrite domain models.
5. Switch between several domain models.

The issue does not persist after page reload, this looks like faulty caching.

  was:
What happens:
AngularJS error is thrown when switching between configuration domain models.
 !the error.png! 

How to reproduce:
1. Start demo mode, launch web agent.
2. Go to configuration and perform DB import once.
3. Open the result configuration domain models section.
4. Import from in place DB, choose to overwrite domain models.
5. Switch between several domain models.

The issue does not persist after page reload, this looks like faulty caching.


> Web console: error in console after configuration import
> --------------------------------------------------------
>
>                 Key: IGNITE-10726
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10726
>             Project: Ignite
>          Issue Type: Bug
>          Components: UI, wizards
>            Reporter: Ilya Borisov
>            Assignee: Vasiliy Sisko
>            Priority: Minor
>         Attachments: the error.png
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> *What happens:*
> AngularJS error is thrown when switching between configuration domain models.
> *How to reproduce:*
> 1. Start demo mode, launch web agent.
> 2. Go to configuration and perform DB import once.
> 3. Open the result configuration domain models section.
> 4. Import from in place DB, choose to overwrite domain models.
> 5. Switch between several domain models.
> The issue does not persist after page reload, this looks like faulty caching.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to