Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mantid becomes unresponsive if data archive service is unavailable #12520

Closed
martyngigg opened this issue May 1, 2015 · 3 comments
Closed

Mantid becomes unresponsive if data archive service is unavailable #12520

martyngigg opened this issue May 1, 2015 · 3 comments
Labels
Framework Issues and pull requests related to components in the Framework High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@martyngigg
Copy link
Member

To reproduce:

Start MantidPlot and make sure that the "Search Data Archive" box is ticket in "Manage User Directories" and remove all other paths. Click Load and type SANS2D28584 into the box. While it is trying to find the file click the browse button and select another file. MantidPlot will then become unresponsive.

Anton was also seeing something similar with the SANS interface and understands how to recreate it.

@martyngigg
Copy link
Member Author

This issue was originally trac ticket 11682

@martyngigg martyngigg added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Framework Issues and pull requests related to components in the Framework labels Jun 3, 2015
@martyngigg martyngigg added this to the Release 3.5 milestone Jun 3, 2015
@rosswhitfield rosswhitfield reopened this Jun 3, 2015
@NickDraper NickDraper modified the milestones: Release 3.5, Release 3.6 Sep 14, 2015
@NickDraper NickDraper modified the milestones: Release 3.6, Release 3.7 Jan 22, 2016
@mantid-roman mantid-roman removed this from the Release 3.7 milestone May 16, 2016
@stale
Copy link

stale bot commented Feb 23, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 23, 2021
@stale
Copy link

stale bot commented Mar 2, 2021

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.

@stale stale bot closed this as completed Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants