Commit Graph

11 Commits (e84b19613e2bfc4ed44e3f6350b23f6c2e01e9e3)

Author SHA1 Message Date
Peter Šurda 32f1e0447a
Multiprocessing PoW fixes and improvements
- the multiprocessing PoW should now work correctly
- it also should be interruptible correctly and the GUI will ask about
  it during exit
7 years ago
Peter Šurda 47e2df86b9
Freezing message parser fix #2
- this has been tested on Windows as well, and has been cleaned up.
  There is now a permanent parser thread, and it restarts when the
  parsing takes more than 1 second
- Fixes #900
7 years ago
Peter Šurda 8f194296e7
Long message parsing fix
- while 448ceaa74c fixed slow rendering on
  windows, there was still a bug where overly long messages caused
  freezeing of the hyperlink regexp parser, which appears to happen on
  all platforms. Maybe it's a freeze, maybe it just takes too long. This
  patch aborts the regexp parser after 1 second and simply displays the
  message without hyperlinks being clickable. This doesn't affect HTML
  mode because there the links are kept as they are
- Fixes #900
7 years ago
Peter Šurda e6ce73f4bd
Multiple PoW updates
- fixes "fast python" (multiprocessing) PoW
- python PoW (both slow and fast) interruptible on *NIX
- signal handler should handle multiple processes and threads correctly
(only tested on Linux)
- popul window asking whether to interrupt PoW when quitting QT GUI
- PoW status in "sent" folder fixes and now also displays broadcast
status which didn't exist before
- Fixes #894
7 years ago
Peter Šurda 4865659d72
Main process fixes
- handles old dialog versions better if using curses
- can spawn SMTP delivery thread if configured (only when in daemon
- daemonized mode now works more like it's properly supposed to on unix
  (double fork etc). You may have to adjust your init scripts, when
  when using upstart for example you should now use "expect daemon"
- daemon mode now cleanly shuts down when TERM/INT signal is received
8 years ago
mirrorwish a7ec4c0555 Some preparations for python 3 8 years ago
mailchuck 4f26bf1059 private IP range checks
When advertising nodes and when establishing connections, private IP
range checks were not done. This could cause private IPs to be
advertised across the network. Also, some of the checks weren't
Fixes Bitmessage#768
8 years ago
antius 41ba921626 Simplify and optimize 10 years ago
antius 53a3d1635a Make addDataPadding method to avoid clutter. 10 years ago
Jordan Hall 2eb6558cf1 Added a number of missing imports fixing several issues (thank you PyDev) 11 years ago
DivineOmega 8f81c35a6f Split off a few generic functions and Bitcoin related functions in seperate helper files 11 years ago