FrederikBaerentsen/BrickTracker
7
19
Fork 11
Code Issues 10 Pull Requests Actions Packages Projects 1 Releases 8 Wiki Activity

[Bug] RLock(s) were not greened (...) #95

New Issue
Closed
opened 2025-09-23 15:11:25 +02:00 by Ventje23 · 4 comments
Ventje23 commented 2025-09-23 15:11:25 +02:00
Copy Link

Hello,

upgraded to version 1.2.4.
When I start my docker container I get this error-message in my log:

RLock(s) were not greened, to fix this error make sure you run eventlet.monkey_patch() before importing any other modules

More out there that experience the same thing?

No idea how to solve this, probably/maybe a code thing

Hello, upgraded to version 1.2.4. When I start my docker container I get this error-message in my log: RLock(s) were not greened, to fix this error make sure you run eventlet.monkey_patch() before importing any other modules More out there that experience the same thing? No idea how to solve this, probably/maybe a code thing
FrederikBaerentsen commented 2025-09-23 15:14:21 +02:00
Owner
Copy Link

I see, i actually get the same message, but since the application didn't have any other errors i ignored it for now. I'll add it to my backlog and fix it in next release.

I see, i actually get the same message, but since the application didn't have any other errors i ignored it for now. I'll add it to my backlog and fix it in next release.
FrederikBaerentsen added the Kind/Bug label 2025-09-23 15:14:25 +02:00
FrederikBaerentsen added this to the Version 1.3 milestone 2025-09-23 15:14:27 +02:00
FrederikBaerentsen added this to the General Improvements project 2025-09-23 15:14:28 +02:00
FrederikBaerentsen self-assigned this 2025-09-23 15:14:31 +02:00
FrederikBaerentsen commented 2025-09-23 16:00:31 +02:00
Owner
Copy Link

Switching from eventlet to gevent fixed the issue.

Switching from eventlet to gevent fixed the issue.
FrederikBaerentsen commented 2025-09-23 17:20:55 +02:00
Owner
Copy Link

@Ventje23 Can you test the tag :1.2.4? It should be fixed now. I'll push to latest, if you can confirm that it works. Please check the docker logs and that adding sets works (socket should say connected).

@Ventje23 Can you test the tag `:1.2.4`? It should be fixed now. I'll push to latest, if you can confirm that it works. Please check the docker logs and that adding sets works (socket should say connected).
FrederikBaerentsen changed title from RLock(s) were not greened (...) to [Bug] RLock(s) were not greened (...) 2025-09-23 17:44:11 +02:00
FrederikBaerentsen removed this from the Version 1.3 milestone 2025-09-23 17:44:15 +02:00
FrederikBaerentsen moved this to In Progress in General Improvements on 2025-09-24 22:06:28 +02:00
FrederikBaerentsen moved this to Needs testing in General Improvements on 2025-09-24 22:06:42 +02:00
FrederikBaerentsen added the
Reviewed
Confirmed
 label 2025-09-26 14:20:23 +02:00
FrederikBaerentsen moved this to Done in General Improvements on 2025-09-27 16:26:22 +02:00
FrederikBaerentsen commented 2025-09-27 16:27:19 +02:00
Owner
Copy Link

Fixed. Released on 1.2.4. Will be in latest when 1.3.0 releases

Fixed. Released on 1.2.4. Will be in `latest` when 1.3.0 releases
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
 Out of Scope
Request is out of scope
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Unraid
Unsupported/Can't help
No Label Kind/Bug
Reviewed
Confirmed
Milestone
No items
No Milestone
Projects
Clear projects
No project General Improvements
Assignees
Clear assignees
FrederikBaerentsen
No Assignees FrederikBaerentsen
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#95
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?