You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to get available packet
Message id is 4
Received a solver data message.
Inserting 1727 transient entries for the standing query.
Inserting 1727 transient entries for the standing query.
Inserting 1727 transient entries for the standing query.
Inserting 1727 transient entries for the standing query.
Inserting 1727 transient entries for the standing query.
Trying to get available packet
Message id is 4
Received a solver data message.
Inserting 1736 transient entries for the standing query.
Inserting 1736 transient entries for the standing query.
Inserting 1736 transient entries for the standing query.
Inserting 1736 transient entries for the standing query.
Inserting 1736 transient entries for the standing query.
Received a cancel request
Received a cancel request
Received a cancel request
Received a cancel request
Received a cancel request
Solver thread error in streaming thread: std::bad_alloc
The text was updated successfully, but these errors were encountered:
Message id is 4
Received a solver data message.
Inserting 1759 transient entries for the standing query.
Inserting 1759 transient entries for the standing query.
Trying to get available packet
Message id is 4
Received a solver data message.
Inserting 1773 transient entries for the standing query.
Inserting 1773 transient entries for the standing query.
Trying to get available packet
Message id is 4
Received a solver data message.
Inserting 1753 transient entries for the standing query.
Inserting 1753 transient entries for the standing query.
Received a cancel request
Received a cancel request
Received a cancel request
Received a cancel request
Received a cancel request
Received a cancel request
Disabling on_demand link average on uri pattern .*
Segmentation fault
Not a problem with the cancel request per se, rather it has to do with the general locking control of the streaming data. A refactor would do this some good.
Trying to get available packet
Message id is 4
Received a solver data message.
Inserting 1727 transient entries for the standing query.
Inserting 1727 transient entries for the standing query.
Inserting 1727 transient entries for the standing query.
Inserting 1727 transient entries for the standing query.
Inserting 1727 transient entries for the standing query.
Trying to get available packet
Message id is 4
Received a solver data message.
Inserting 1736 transient entries for the standing query.
Inserting 1736 transient entries for the standing query.
Inserting 1736 transient entries for the standing query.
Inserting 1736 transient entries for the standing query.
Inserting 1736 transient entries for the standing query.
Received a cancel request
Received a cancel request
Received a cancel request
Received a cancel request
Received a cancel request
Solver thread error in streaming thread: std::bad_alloc
The text was updated successfully, but these errors were encountered: