Bitmessage/PyBitmessage-2025-02-22
Archived
2
0
Fork 0
Code Issues 167 Pull Requests 54 Actions Packages Projects Releases 5 Wiki Activity

Object processor queue starts too early #1702

New Issue
Closed
opened 2021-01-03 11:01:44 +01:00 by PeterSurda · 0 comments
PeterSurda commented 2021-01-03 11:01:44 +01:00 (Migrated from github.com)
Copy Link

Received a report. Looks like objectProcessor starts before sqlThread is ready. I can't actually reproduce it, it probably only happens if the objectProcessorQueue isn't empty under non-deterministic conditions. The problem was revealed in 184664d758. The solution is for the objectProcessor.__init__ to wait for the helper_sql.sql_ready event.

2021-01-03 06:30:31,908 - CRITICAL - Unhandled exception
Traceback (most recent call last):
  File "Documents/Software/PyBitmessage/src/bitmessagemain.py", line 491, in <module>
  File "Documents/Software/PyBitmessage/src/bitmessagemain.py", line 487, in main
  File "Documents/Software/PyBitmessage/src/bitmessagemain.py", line 286, in start
  File "/home/*****/Documents/Software/PyBitmessage/src/class_objectProcessor.py", line 54, in __init__
    '''SELECT objecttype, data FROM objectprocessorqueue''')
  File "/home/*****/Documents/Software/PyBitmessage/src/helper_sql.py", line 44, in sqlQuery
    assert sql_available
AssertionError
Number of threads: 1

Operating system is Ubuntu 18.04.5 LTS 32-bit.
Received a report. Looks like `objectProcessor` starts before `sqlThread` is ready. I can't actually reproduce it, it probably only happens ~if the `objectProcessorQueue` isn't empty~ under non-deterministic conditions. The problem was revealed in 184664d7583096e6cd7b828e08d112ff1727d81b. The solution is for the `objectProcessor.__init__` to wait for the `helper_sql.sql_ready` event. ``` 2021-01-03 06:30:31,908 - CRITICAL - Unhandled exception Traceback (most recent call last): File "Documents/Software/PyBitmessage/src/bitmessagemain.py", line 491, in <module> File "Documents/Software/PyBitmessage/src/bitmessagemain.py", line 487, in main File "Documents/Software/PyBitmessage/src/bitmessagemain.py", line 286, in start File "/home/*****/Documents/Software/PyBitmessage/src/class_objectProcessor.py", line 54, in __init__ '''SELECT objecttype, data FROM objectprocessorqueue''') File "/home/*****/Documents/Software/PyBitmessage/src/helper_sql.py", line 44, in sqlQuery assert sql_available AssertionError Number of threads: 1 Operating system is Ubuntu 18.04.5 LTS 32-bit. ```
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working as it's supposed to
build
Related to building or build system
dependencies
Pull requests that update a dependency file
developers
The issue is relevant mainly for developers rather than users
documentation
duplicate
enhancement
New feature
formatting
Code or UI text formatting
invalid
legal
mobile
Frontend for mobile devices (kivy)
obsolete
packaging
performance
protocol
Protocol change
question
refactoring
regression
Some issue, fixed in the past, appears again
security
test
translation
usability
wontfix
No Label
bug
Milestone
No items
No Milestone v0.6.4
Projects
Clear projects
No project
Assignees
Clear assignees
PeterSurda
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-22#1702
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?