Skip to content
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

Are many 140.X workflows intentionally not processing any Events? #44563

Open
makortel opened this issue Mar 27, 2024 · 6 comments
Open

Are many 140.X workflows intentionally not processing any Events? #44563

makortel opened this issue Mar 27, 2024 · 6 comments

Comments

@makortel
Copy link
Contributor

In #44413 it was noticed that at least workflows 140.X where X is 004, 006, 007, 008, 009, 011, 021 do not process any Events. While this was great to uncover the problem investigated in #44413, a question remains if that was intentional, or if these workflows were intended to process Events?

@makortel
Copy link
Contributor Author

assign pdmv

@cmsbuild
Copy link
Contributor

New categories assigned: pdmv

@AdrianoDee,@sunilUIET,@miquork you have been requested to review this Pull request/Issue and eventually sign? Thanks

@cmsbuild
Copy link
Contributor

cms-bot internal usage

@cmsbuild
Copy link
Contributor

A new Issue was created by @makortel.

@smuzaffar, @makortel, @Dr15Jones, @antoniovilela, @rappoccio, @sextonkennedy can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

@AdrianoDee
Copy link
Contributor

AdrianoDee commented Mar 29, 2024

Hi Matti, I really doubt this was intentional at the time of their introduction. So:

  1. I'm having a look to have them better defined;
  2. given the accidental usefulness of this kind of wfs would anyway makes sense to keep one of them with the explicit intention to check these unusual conditions? This time intentionally.

@makortel
Copy link
Contributor Author

makortel commented Apr 1, 2024

2. given the accidental usefulness of this kind of wfs would anyway makes sense to keep one of them with the explicit intention to check these unusual conditions? This time intentionally.

I think keeping one such "no events" workflow would indeed be useful.

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

No branches or pull requests

3 participants