[
https://issues.apache.org/jira/browse/IGNITE-11717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816158#comment-16816158
]
Ilya Borisov commented on IGNITE-11717:
---------------------------------------
[~kuaw26] the fix looks good to me, if it works. Maybe add a unit/e2e test?
> Web console: project generation runtime error caused by IGFS
> ------------------------------------------------------------
>
> Key: IGNITE-11717
> URL: https://issues.apache.org/jira/browse/IGNITE-11717
> Project: Ignite
> Issue Type: Bug
> Components: wizards
> Reporter: Ilya Borisov
> Assignee: Alexey Kuznetsov
> Priority: Major
> Attachments: image-2019-04-10-17-52-48-599.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *What happens:*
> Runtime error in console.
> !image-2019-04-10-17-52-48-599.png!
> How to reproduce:
> 1. Go to cluster configuration/create igfs.
> 2. Choose "Caching" FS factory.
> 3. Choose "Chained" user name mapper.
> 4. Open new mapper sub form, choose custom.
> 5. Change FS factory a couple of time, change it back to "Caching".
> 6. Do the same with with "Name mapper" select, change it back to "Custom".
> 7. If the error does not happen, play around by changing other select values.
> *Expected behavior:*
> Run time error should not happen.
> This happens in master. [~vsisko] I think you should look into why `bean` is
> `null` or handle this case gracefully.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
