I am running a flow and receive the following error message:
java.lang.IllegalStateException: Was expecting to find transaction set
on current strand: Thread[Mock node 1 thread,5,main]
And:
Terminated by unexpected exception {} java.lang.AssertionError:
Unexpected task state (fiber parking or parked has no chance to to
call park): -2 at
co.paralleluniverse.fibers.RunnableFiberTask.park(RunnableFiberTask.java:213)
~[quasar-core-0.7.9-jdk8.jar:0.7.9] at
What is the cause of this issue?
This issue was caused by calling a custom lambda method from within my flow:
myMethod {
subflow(xyz)
}
If the method is converted to a method without a lambda, the error disappears.
This is due to an issue in how Quasar serialises Kotlin lambdas.
Related
What can the following be due to / how to debug it? it happens when closing my MPI application
[1612979755.727913] [compute-0-9:21112:0] tag_match.c:61 UCX WARN unexpected tag-receive descriptor 0x2b2bf64cdbc0 was not matched
Assuming the application exited normally, this probably means that some process sent a message (e.g. calling MPI_Send) to a destination process that did not post a matching receive before calling MPI_Finalize. See https://github.com/openucx/ucx/issues/6331#issuecomment-778428537
I am copying data from one Cosmosdb collection to another within the same account.
I am getting following exception
{"StatusCode":"DFExecutorUserError","Message":"Job failed due to
reason: Errors encountered in bulk update API execution. Number of
failures corresponding to exception of type:
java.lang.RuntimeException = 500; FAILURE: java.lang.RuntimeException:
Stored proc returned failure 404\n\tat
com.microsoft.azure.documentdb.bulkexecutor.internal.BatchUpdater$1.call(BatchUpdater.java:199)\n\tat
com.microsoft.azure.documentdb.bulkexecutor.internal.BatchUpdater$1.call(BatchUpdater.java:148)\n\tat
com.microsoft.azure.documentdb.repackaged.com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:125)\n\tat
com.microsoft.azure.documentdb.repackaged.com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:57)\n\tat
com.microsoft.azure.documentdb.repackaged.com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78)\n\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat
java.util.concurrent.ThreadPoo","Details":"Errors encountered in bulk
update API execution. Number of failures corresponding to exception of
type: java.lang.RuntimeException = 500; FAILURE:
java.lang.RuntimeException: Stored proc returned failure 404\n\tat
com.microsoft.azure.documentdb.bulkexecutor.internal.BatchUpdater$1.call(BatchUpdater.java:199)\n\tat
com.microsoft.azure.documentdb.bulkexecutor.internal.BatchUpdater$1.call(BatchUpdater.java:148)\n\tat
com.microsoft.azure.documentdb.repackaged.com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:125)\n\tat
com.microsoft.azure.documentdb.repackaged.com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:57)\n\tat
com.microsoft.azure.documentdb.repackaged.com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78)\n\tat
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat
java.util.concurrent.ThreadPoolExecutor$Worker.run(Threa"}
Sharing the answer as per the comment by the original poster:
It started to work after multiple retries.
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.data.elasticsearch.repository.support.NumberKeyedRepository]: Constructor threw exception; nested exception is com.github.vanroy.springdata.jest.exception.JestElasticsearchException: Cannot execute jest action , response code : 400 , error : {"root_cause":[{"type":"index_already_exists_exception","reason":"index [user/37YxejngRkiJQ4GXn082kQ] already exists","index_uuid":"37YxejngRkiJQ4GXn082kQ","index":"user"}],"type":"index_already_exists_exception","reason":"index [user/37YxejngRkiJQ4GXn082kQ] already exists","index_uuid":"37YxejngRkiJQ4GXn082kQ","index":"user"} , message : null
I wrote a SBT task to run cssLint for my project using rhino. cssLint returns exit code to my SBT task.
My question is how to make the task fail if the exit code is non-zero?
I don't want to throw any exceptions. I want my last line of the task result to show [Failed] instead of [success] and exit code of my SBT task to be non-zero.
SAMPLE
MyTask {
val exitcode = //rhino functions
//what to do??
}
The actual intent is to fail the build if css errors are present.
The way of failing the build without producing the stacktrace on the console is using the exceptions that are specifically handled:
for sbt.MessageOnlyException an error message is logged twice (without task name and then with task name) and the build is stopped
mix in sbt.FeedbackProvidedException or sbt.UnprintableException to implement custom exceptions for which sbt does not print a stacktrace. The string with task name and exception's toString is logged on the top level once and the build is stopped. It is expected that essential information for the user is already logged before throwing these.
Disclaimer: I've not seen this information in sbt manual. Extracted from the sources of sbt 0.13.16. sbt.FeedbackProvidedException is used this way by sbt compiler, sbt tests and by sbt-web and Play sbt plugins.
My understanding is that the success message is printed out always unless
showSuccess setting is set to false or
a task throws an exception.
In your particular case you want to report an error and so you should throw an exception or a value of the type of the result that might be considered a sort of exception like None or Failure.
Say, you've got the following task defined in build.sbt:
lazy val tsk = taskKey[Unit]("Task that always fails")
tsk := {
throw new IllegalStateException("a message")
}
When you execute the tsk task, the exception is printed out with no [success] afterwards.
[no-success]> tsk
[trace] Stack trace suppressed: run last *:tsk for the full output.
[error] (*:tsk) java.lang.IllegalStateException: a message
[error] Total time: 0 s, completed Feb 15, 2014 11:45:27 PM
I would rather prefer avoiding this style of programming and rely on Option as a way to report an issue with processing.
With the following tskO definition:
lazy val tskO = taskKey[Option[String]]("Task that reports failure as None")
tskO := None
you'd then check the result and if it's None you'd know it's a failure.
I've modified the code at http://www.switchonthecode.com/tutorials/using-core-plot-in-an-iphone-application to run on xcode4, I have a view that I put into my ConsoleViewControllor.xib with its class as CPTGraphHostingView.
Compiles great, at runtime however, I get a SIGABRT at line
hostingView.hostedGraph = graph; with the error
* Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[UIView setHostedGraph:]: unrecognized selector sent to instance 0x5910d40'
* Call stack at first throw:
Anyone else run into this issue? I'm more than willing to give you code and answer more questions. Thanks in advance!
Check the setup in your .xib again. -[UIView setHostedGraph:] means that Xcode created a UIView, not a CPTGraphHostingView.