BitShares Forum
Main => Technical Support => Topic started by: monsterer on December 12, 2015, 05:59:42 pm
-
I've suddenly started getting this message - I have upgraded to the latest bitshares hardforking release. I've not seen this error in the previous version, any idea what it means?
-
I've been receiving this message intermittently for weeks, I think it might be triggered by RPC calls. Not sure what it means, I assumed it was just an innocuous debug message
-
I've been receiving this message intermittently for weeks, I think it might be triggered by RPC calls. Not sure what it means, I assumed it was just an innocuous debug message
if( _subscribe_callback ) {
for( auto id : ids )
{
if( id.type() == operation_history_object_type && id.space() == protocol_ids ) continue;
if( id.type() == impl_account_transaction_history_object_type && id.space() == implementation_ids ) continue;
this->subscribe_to_item( id );
}
}
else
{
elog( "getObjects without subscribe callback??" );
}
Would seem so.
-
The reason for this warning is that the witness node expects users to first "register" with the database api before they query for database stuff ..
In this case you asked something from the database and haven't requested access to the database yet
http://docs.bitshares.eu/api/websocket.html#requesting-api-access
-
The reason for this warning is that the witness node expects users to first "register" with the database api before they query for database stuff ..
In this case you asked something from the database and haven't requested access to the database yet
http://docs.bitshares.eu/api/websocket.html#requesting-api-access
Not quite. The reason for this is an assumption that the GUI wants push notifications of changes to any object it has queried. This message was put there to detect instances where the GUI was misusing the API. However, it can safely be ignored if you don't care about getting updates. We can probably delete the warning all together.