CRITICAL - Error! Bug! The class_objectProcessor was passed an object type it doesn't recognize #1023

Closed
opened 2017-07-04 16:09:39 +02:00 by Erkan-Yilmaz · 3 comments
Erkan-Yilmaz commented 2017-07-04 16:09:39 +02:00 (Migrated from github.com)

I see:

2017-06-27 17:37:06,088 - CRITICAL - Error! Bug! The class_objectProcessor was passed an object type it doesn't recognize: 10
2017-07-01 11:02:05,742 - CRITICAL - Error! Bug! The class_objectProcessor was passed an object type it doesn't recognize: 10

and then 195 more entries with the number 4797008 at end (from July 1 until today), e.g.:

2017-07-04 14:31:41,040 - CRITICAL - Error! Bug! The class_objectProcessor was passed an object type it doesn't recognize: 4797008
  • BM node running over tor, started on July 24
  • dev 0.6 branch with commit: 189578c

on request further info is available

I see: 2017-06-27 17:37:06,088 - CRITICAL - Error! Bug! The class_objectProcessor was passed an object type it doesn't recognize: 10 2017-07-01 11:02:05,742 - CRITICAL - Error! Bug! The class_objectProcessor was passed an object type it doesn't recognize: 10 and then 195 more entries with the number 4797008 at end (from July 1 until today), e.g.: 2017-07-04 14:31:41,040 - CRITICAL - Error! Bug! The class_objectProcessor was passed an object type it doesn't recognize: 4797008 * BM node running over tor, started on July 24 * dev 0.6 branch with commit: 189578c on request further info is available
g1itch commented 2017-07-04 17:29:53 +02:00 (Migrated from github.com)

I got the same error with latest code:
2017-07-04 18:21:55,451 - CRITICAL - Error! Bug! The class_objectProcessor was passed an object type it doesn't recognize: 4797008

Also running BM over tor.

I got the same error with latest code: `2017-07-04 18:21:55,451 - CRITICAL - Error! Bug! The class_objectProcessor was passed an object type it doesn't recognize: 4797008` Also running BM over tor.
PeterSurda commented 2017-07-05 08:47:40 +02:00 (Migrated from github.com)

This is an overly dramatic log entry. I actually have it fixed locally and will commit it in the next day or two. The object is an IP2 address created by MiNode.

This is an overly dramatic log entry. I actually have it fixed locally and will commit it in the next day or two. The object is an IP2 address created by MiNode.
TheKysek commented 2017-07-05 20:29:38 +02:00 (Migrated from github.com)

I2P*

I2P*
This repo is archived. You cannot comment on issues.
No Milestone
No project
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2024-12-06#1023
No description provided.