Closed aaroncox closed 7 months ago
I have not tested your config.ini
, however doesn't look like you are specifying eosio::chain_api_plugin
as it is on the same line as eosio::chain_plugin
.
plugin = eosio::chain_plugin eosio::chain_api_plugin
plugin = eosio::chain_plugin
plugin = eosio::chain_api_plugin
That's a valid way of specifying plugins because of this oddity, https://github.com/AntelopeIO/appbase/blob/main/application_base.cpp#L404 so it makes sense why, https://github.com/AntelopeIO/leap/blob/4531e9751a8d6d712801ffab1e2b24fe37dc9ca8/plugins/producer_plugin/producer_plugin.cpp#L1223 wouldn't find it.
Wow good catch... and that's quite the obscure bug 😂
We have specified multiple plugins on the same line like that since EOS launched, kind of grouping the ones that go together on the same line to enable/disable the pairing at the same time.
I'll understand based on this situation though if moving forward we should deprecate that method of specifying plugins.
Current fix is not finding chain_api_plugin
initialized
during producer_plugin
initialize on hotstuff_integration
branch.
On v5.0.0, without providing
read-only-theads
in the config.ini - the/v1/chain/send_read_only_transaction
API endpoint does not work.Against a Jungle4 testnet node, if I execute the following query:
The response from curl is:
Now if I modify the config and add
read-only-theads = 4
, and rerun the same curl command, I get a response:The configuration that is causing the error is as follow, with
read-only-threads
commented out.Any ideas?