Prism prevents edition of Sprint with some issues

[Yves Martin]

 Hello

I have a odd behaviour to report - for a small set of users of a specific project where a Sprint "RE 3.0" was shared in two Agile Scrum Boards (was - because I have deleted one during investigations)

Symptoms for that users on a specific issue+sprint:

1. When clicking on "Sprint" pencil, the drop-down list is just empty - a JS "Range length error" on batch.js is visible in console - lines come from Prism plugin.
2. When using "Edit" button, endless waiting wheel...

As administrator, everything works as expected - both Sprint edit or global issue edit.

Because of clues that "Prism" may be involved, I have disabled plugin - and troubles are simply fixed. Users can now edit Sprint value and issue.

How should I go further in diagnostic to understand what is wrong and get it fixed properly in plugin?

[Siavash Safi]

@Yves MartinI received a similar issue reported before from a user last year:

Uncaught RangeError: Invalid array length
 

The root cause turned out to be `{code]`, unfortunately I was not able to handle this internal JS exception caused by invalid user input.

Try looking for a similar syntax error in code blocks.

Also we recently released a new version including changes in the upstream PrismJS which might prevent this exception.