Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
type plugin not mounted #2384
Steps to Reproduce the Problem
Do as instructed in examples/highlevel:
cd examples/highlevel sudo kdb mount spec.ini 'spec/sw/example/highlevel/#0/current' ni sudo kdb import 'spec/sw/example/highlevel/#0/current' ni < spec.ini sudo kdb spec-mount '/sw/example/highlevel/#0/current'
and then try to set an invalid value:
kdb set /sw/example/highlevel/#0/current/myint abc
That it fails with an type error.
Further Log Files and Output
It seems like the type plugin is not mounted and #2377 did not improve the situation:
Yes, it is weird but understandable: the hexnumber plugin also provides "type" as meta data. It is preferred because it has a better score in
So we either:
Shouldn't we just mount all plugins that use a certain metadata? If certain plugins would conflict with each other, we should have a way to state that in the
One of these would be the quick solution. Type dispatcher seems like a good idea, but would probably take some time. If we want to elektrify LCDproc without C++ dependencies, we need to rewrite the
No, a plugin providing metadata means that the plugin fulfills this property. Otherwise non-idempotent actions like renaming would not work.
This is quite problematic because then you need an NP-complete solver to find the correct plugins. It is also quite error-prone to specify all conflicts correctly. (and assumes a closed world)
Yes, a type plugin written in C that checks for the basic types and calls other validation plugins if
Well in that case