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
One of the issues IDA struggles with (in regard to events) is that some of their 'gated' event notifications may fail without notification. BN also seems to suffer from this.
By 'gated' events mean an event callback that happens before a certain piece of information is modified in the database, and an event callback that happens after it is modified.
For example, in BinaryDataNotifications we have:
BEFORE - function_update_requested
AFTER - function_updated
As a plugin developer, I may want to hook function_update_requested to capture some information prior to this object being modified. My hooks then may change their logic to wait for a function_updated event to come through.
But in failure cases, the function_updated event may never get fired off. As a result, my logic is now stuck in a state waiting for an event that may never come (or recieve a completely different one later).
If these gated events cannot complete, you should send out a notification as such:
FAILURE - function_update_canceled
In slack, rss noted that `this might be worth a ticket, my recollection of that path makes that seem like it wouldn't be hard to add'. Filing this so it doesn't get lost.
The text was updated successfully, but these errors were encountered:
One of the issues IDA struggles with (in regard to events) is that some of their 'gated' event notifications may fail without notification. BN also seems to suffer from this.
By 'gated' events mean an event callback that happens before a certain piece of information is modified in the database, and an event callback that happens after it is modified.
For example, in BinaryDataNotifications we have:
As a plugin developer, I may want to hook
function_update_requested
to capture some information prior to this object being modified. My hooks then may change their logic to wait for afunction_updated
event to come through.But in failure cases, the
function_updated
event may never get fired off. As a result, my logic is now stuck in a state waiting for an event that may never come (or recieve a completely different one later).If these gated events cannot complete, you should send out a notification as such:
In slack, rss noted that `this might be worth a ticket, my recollection of that path makes that seem like it wouldn't be hard to add'. Filing this so it doesn't get lost.
The text was updated successfully, but these errors were encountered: