-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Observer Improvements #6397
Observer Improvements #6397
Conversation
filmor
commented
Oct 27, 2022
- Allow starting the observer connected to a node
- Ignore repeated nodedown messages
CT Test Results 2 files 15 suites 15m 25s ⏱️ Results for commit bdbd83b. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts// Erlang/OTP Github Action Bot |
Fix typo and test that it works as you intended because it can't right now. |
d502de4
to
8bed574
Compare
This works:
Add test cases and update documentation with new functions, |
It does what I want it to now, namely, I can start the observer like this now:
|
Can you fix the doc build problems? |
5689fd9
to
94f7b86
Compare
Test fail
|
I saw that there is an undocumented function |
You have some timing issues. But looking at the code again, shouldn't the Node argument be sent observer_wx:start() function and be handled there |
Hmm, the timing issues are odd, shouldn't the startup be synchronous? Or are the 500ms just not enough for a wx app? I figured that |
The sleep in the first testcase is needed because observers startup is not synchronous, and the code deadlocks it self when you call observer:stop(). The second sleep is needed because you do a monitor on the observer process which may not have started yet, i.e. directly after the spawn(). Regarding the set_node(), I see your point so let me ponder on that for a while before you re-write it. |
Okay, I'll add the sleeps. I'll also have a look whether I can make the startup synchronous in a separate PR. |
195fade
to
bdbd83b
Compare
Great, thank you :) |