-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Move BSQ price in USD at first row #4988
Move BSQ price in USD at first row #4988
Conversation
Travis has lots of issues recently...
|
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 would give this a Tested ACK
right now, but will delay until you have seen what happens if I click the DAO
menu item why the initial sync is in progress:
Dec-24 13:20:17.737 [JavaFX Application Thread] INFO b.c.d.n.p.BlockParser: Parsing 0 transactions at block height 658790 took 0 ms
Dec-24 13:20:17.843 [JavaFX Application Thread] INFO b.c.d.n.p.BlockParser: Parsing 5 transactions at block height 658791 took 0 ms
Dec-24 13:20:17.944 [JavaFX Application Thread] INFO b.c.d.n.p.BlockParser: Parsing 1 transactions at block height 658792 took 0 ms
Dec-24 13:20:17.974 [NetworkNode:SendMessage-to-n55uir3nbux3oerkmldrqiua3tvxedtcqggr5k4rprzvttqk3xawdhid.onion:9999] INFO b.n.p.n.NetworkNode: Socket creation to peersNodeAddress n55uir3nbux3oerkmldrqiua3tvxedtcqggr5k4rprzvttqk3xawdhid.onion:9999 took 15216 ms
Dec-24 13:20:18.391 [JavaFX Application Thread] ERROR b.c.s.CommonSetup: Uncaught Exception from thread JavaFX Application Thread
Dec-24 13:20:18.391 [JavaFX Application Thread] ERROR b.c.s.CommonSetup: throwableMessage= null
Dec-24 13:20:18.391 [JavaFX Application Thread] ERROR b.c.s.CommonSetup: throwableClass= class java.lang.NullPointerException
Dec-24 13:20:18.393 [JavaFX Application Thread] ERROR b.c.s.CommonSetup: Stack trace:
java.lang.NullPointerException
at bisq.desktop.components.JFXTextFieldSkinBisqStyle.updateTextPos(JFXTextFieldSkinBisqStyle.java:95)
at bisq.desktop.components.JFXTextFieldSkinBisqStyle.layoutChildren(JFXTextFieldSkinBisqStyle.java:79)
at javafx.scene.control.Control.layoutChildren(Control.java:601)
at javafx.scene.Parent.layout(Parent.java:1204)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Parent.layout(Parent.java:1211)
at javafx.scene.Scene.doLayoutPass(Scene.java:576)
at javafx.scene.Scene$ScenePulseListener.pulse(Scene.java:2482)
at com.sun.javafx.tk.Toolkit.lambda$runPulse$2(Toolkit.java:412)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:389)
at com.sun.javafx.tk.Toolkit.runPulse(Toolkit.java:411)
at com.sun.javafx.tk.Toolkit.firePulse(Toolkit.java:438)
at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:519)
at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:499)
at com.sun.javafx.tk.quantum.QuantumToolkit.pulseFromQueue(QuantumToolkit.java:492)
at com.sun.javafx.tk.quantum.QuantumToolkit.lambda$runToolkit$11(QuantumToolkit.java:320)
at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:96)
at com.sun.glass.ui.gtk.GtkApplication._runLoop(Native Method)
at com.sun.glass.ui.gtk.GtkApplication.lambda$runLoop$11(GtkApplication.java:277)
at java.base/java.lang.Thread.run(Thread.java:835)
Dec-24 13:20:18.395 [JavaFX Application Thread] INFO b.n.p.p.PeerManager: Num of latestLivePeers=9
Dec-24 13:20:18.414 [JavaFX Application Thread] INFO b.c.d.n.p.BlockParser: Parsing 0 transactions at block height 658793 took 0 ms
Dec-24 13:20:18.577 [JavaFX Application Thread] INFO b.c.d.n.p.BlockParser: Parsing 1 transactions at block height 658794 took 0 ms
Dec-24 13:20:18.702 [JavaFX Application Thread] INFO b.c.d.n.p.BlockParser: Parsing 0 transactions at block height 658795 took 0 ms
I assume that happens on master version as well. From my trivial changes I don't see how that can have caused it. |
It is related to jfoenix 9.0.6's use of reflection.
|
Or maybe we access some data which is not set at sync time... its a pity that exceptions in the UI dont show a useful stack trace... Maybe we should wrap all activate and initialize methods with try catch and print the stack trace... |
But I guess you are right and its a JFX library bug:
line there is:
Do you run JDK 12? Seems there are issues: |
I use OpenJDK 11 and 12 with v 10 src and target compatibility. I believe the problem is not so easy to solve, since jfoenix 9.0.6 is not compatible with JDK 11+, and jfoenix 9.10.0 is not backward compatible -- and we're still stuck with shipping JDK 10 binaries due to the jpackager problem. We've bumped into this problem many times, including this PR which was backed out. |
I think we could get rid of the jfoenix dependency altogether without too much difficulty. |
I take that back, there are too many jfoenix controls to say removing the dependency would be easy. |
I think there was a jvm arg to be passed which fixed it... or use jdk 10 for now. I think we are close anyway for the JDK update. That should resolve it as well. |
You're right, the NPE does not appear when building & running on JDK 10. I tried using jfoenix's 9.0.10 ReflectionHelper, and that worked in JDK 11, but not JDK 12. I don't know which jvm arg might avoid it. I tried |
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.
utACK
The USD price is more relevant for the DAO than the BSQ/BTC price. Also the arrow if price goes up or down is more stable and meaningful for the USD pair than for BTC as BTC price can be very volatile.