Confusing error message when loading backend twice
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing the plugin-loading path that checks whether the number of registered backends increased, then inspect how backend constructor creator functions are registered. Reproduce loading the same backend twice and confirm that an already-registered backend no longer produces the misleading invalid-plugin error.
Written by the indexing model from the issue text.
Description
When loading a backend twice, it is only registered the first time, which is ok because it is already known.
However, an error message is printed:
Error: Caught exception loading plugin '/export/doocs/server/llrfCtrl_server/libChimeraTK-DeviceAccess-DoocsBackend.so' specified in dmap file: '/export/doocs/server/llrfCtrl_server/libChimeraTK-DeviceAccess-DoocsBackend.so' is not a valid DeviceAccess plugin, it does not register any backends!
Some backends will not be available!
Although this will change when the plugin loading mechanism is changes, this is confusing and should be fixed. One could add a function to the backend which checks if the constructor creator function is already registered, instread of just checking that the count of registered backends has increased, which is not true in this case.
- Dominant language
- C++
- Stars
- 12
- Forks
- 12
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 13
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ChimeraTK/DeviceAccess
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
ChimeraTK/DeviceAccess#539 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 52/100
ChimeraTK/DeviceAccess#395 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ChimeraTK/DeviceAccess#285 · 3 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 42/100
ChimeraTK/DeviceAccess#202 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ChimeraTK/DeviceAccess#200 ·
All issues in ChimeraTK/DeviceAccess
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·