Skip to content

Bug in Process class #8087

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
zan-vseved opened this issue May 18, 2013 · 2 comments
Closed

Bug in Process class #8087

zan-vseved opened this issue May 18, 2013 · 2 comments
Labels

Comments

@zan-vseved
Copy link

There seems to be bug in Process class. Run method sometimes returns null. See kriswallsmith/assetic#421

@stof
Copy link
Member

stof commented May 18, 2013

Please give more details about the way to reproduce it

@fabpot
Copy link
Member

fabpot commented Jun 13, 2013

Closing as there is not feedback from the reporter.

@fabpot fabpot closed this as completed Jun 13, 2013
lyrixx added a commit that referenced this issue Jun 26, 2017
…olm)

This PR was submitted for the master branch but it was merged into the 3.2 branch instead (closes #23299).

Discussion
----------

[Workflow] Added more events to the announce function

| Q             | A
| ------------- | ---
| Branch?       | 3.2
| Bug fix?      | yes/no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #23275
| License       | MIT
| Doc PR        | #8087

This PR will fix #23275

The documentation states that we dispatch events `workflow.announce` and `workflow.[name].announce`. It was me who wrongly added it to the docs... sorry about that.

We could either: Change the docs or add these events. I choose to add these event to the source since the same events are dispatched for "guard", "leave", "transition", "enter" and "entered".

Commits
-------

c5042f3 [Workflow] Added more events to the announce function
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

3 participants