Skip to content

Retarget the shadow driver #539

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wzrdtales opened this issue Feb 3, 2018 · 1 comment
Closed

Retarget the shadow driver #539

wzrdtales opened this issue Feb 3, 2018 · 1 comment
Labels

Comments

@wzrdtales
Copy link
Member

wzrdtales commented Feb 3, 2018

Description

The shadow driver was originally added to potentially intervene actions to build up representations of the current state. Since this is not a use case in the db-migrate universe as db-migrate itself has no drivers included in the core at all anymore and only drivers that strictly follow pre-defined standards would fit in, it ended up dangling along.
It is going to be repurposed and is not going to target a single method anymore, but the whole driver. This will allow us to interpret a single instruction of an execution unit before actually running it and leaving this task to a processor. This in turn allows us to get information about the state. Some limitations are implied, such as highly dynamic non monitored tasks, that completely depend upon the direct entry state will not be monitorable and will need some work of thought to mitigate them.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@wzrdtales
Copy link
Member Author

done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant