API clientStatus bug #1383
Labels
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Bitmessage/PyBitmessage-2024-12-18#1383
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
came over BM. I haven't tested it, just crosspasting
In their infinite wisdom the devs have decided on the following logic:
If currently connected networkStatus is 'notConnected'
If not currently connected and have not received any incoming connections. networkStatus is "connectedButHaveNotReceivedIncomingConnections"
Otherwise networkStatus is "connectedAndReceivingIncomingConnections"
Hmm well for me it's been working fine until just recently.
in --curses it never worked even be4
I've been running a headless BM instance for a while and I use the api.clientStatus call to monitor it. I noticed that the networkStatus field says "notConnected" when it's connected and receiving incoming connections.
I don't know if this was today's pull or the one before that introduced it.
Yes, it looks strange. Introduced in
7ed459b
.Previous edition was: