-
Notifications
You must be signed in to change notification settings - Fork 79
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
Setup ExecutionContext in Barrage Client Examples #4461
Conversation
Util/src/main/java/io/deephaven/util/thread/ThreadInitializationFactory.java
Show resolved
Hide resolved
@@ -23,10 +24,20 @@ public interface ThreadInitializationFactory { | |||
return clazz.getDeclaredConstructor().newInstance(); | |||
} catch (ClassNotFoundException | NoSuchMethodException | InvocationTargetException | |||
| InstantiationException | IllegalAccessException e) { | |||
|
|||
// TODO (https://github.com/deephaven/deephaven-core/issues/4040): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the right ticket?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe so; I acquired it from Colin. It is the ticket related to python debug initialization. This snippet can be reverted once Colin takes an alternative approach.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is the ticket (in several parts...) that will address this.
Labels indicate documentation is required. Issues for documentation have been opened: How-to: https://github.com/deephaven/deephaven.io/issues/3162 |
It was recently discovered that the barrage client examples were no longer working. This was a side effect of adding multiple update graph support to the engine.
Additionally, there is server-side configuration that is accessible to the client that requires a class that is only in the server package. This server-side configuration is likely to be reworked in the near future and even possibly the need for this server-side class that can't be loaded. For now, I've modified the thread factory initialization to ignore class not found exceptions within the server-side package.
To work around this while still using a previous release one either needs to provide their own
dh-defaults.prop
file or add the following jvm flag-Dthread.initialization=
to remove the reference to the server-side class.From a documentation perspective, we should add setup instructions for the ticking java-client use case (as otherwise demonstrated by the example).