Feature #9088
closedEnable safe marks by default
0%
Description
When uploading safe marks by a manager failed, I revealed that safe marks are disabled by default. There is a special setting ENABLE_SAFE_MARKS set to False within bridge/common.py. Although everybody can easily set this setting to True, I assume that we can just get rid of it completely (i.e. remove this setting and change all places where it is used appropriately). It was introduced a long ago, when associating safe marks was extremely slow, but now this isn't the case anymore.
BTW this rule seems to be violated by preset safe marks that are populated without any restrictions. So, it isn't working well anyway.
Updated by Evgeny Novikov over 6 years ago
- Related to Feature #9089: Investigate whether disabling safe marks matter added
Updated by Evgeny Novikov over 6 years ago
- Priority changed from Urgent to High
- Target version changed from 1.1 to 2.0
Let's Vladimir will do this after his vacation.
Updated by Vladimir Gratinskiy about 6 years ago
- Status changed from New to Resolved
Implemented in bridge-2.0
Updated by Evgeny Novikov about 6 years ago
- Priority changed from High to Urgent
Updated by Evgeny Novikov about 6 years ago
- Status changed from Resolved to Closed
Tests passed, so, I merged the branch to master in b8bda00ac.