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

Presentation compiler forgets asks #6505

Closed
scabug opened this issue Oct 10, 2012 · 3 comments
Closed

Presentation compiler forgets asks #6505

scabug opened this issue Oct 10, 2012 · 3 comments
Assignees
Milestone

Comments

@scabug
Copy link

@scabug scabug commented Oct 10, 2012

This is a regression since a few months ago. A presentation compiler that is asked to shutdown will cause any thread that calls ask to wait forever for a response. The sequence of calls is the following:

	def askItem(): Response[Unit] = {
		compiler.askForResponse { () =>
			Thread.sleep(100)
			println("inside Ask")
		}
	}

	def main(args: Array[String]) {
		val item1 = askItem()

		compiler.askShutdown()

		Thread.sleep(1000)
		val item2 = askItem()

                item2.get // will never return
       }

The second call to askitem places the work item on a queue that is not serviced anymore.

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Oct 10, 2012

Imported From: https://issues.scala-lang.org/browse/SI-6505?orig=1
Reporter: @dragos
Affected Versions: 2.10.0
Other Milestones: 2.10.0-M7, 2.10.0

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Oct 10, 2012

@gkossakowski said:
Iulian, do you want this to be fixed in 2.10.0? You marked it as critical intentionally, right?

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Oct 11, 2012

@dragos said:
Yes, and the pull request is waiting for reviewers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.