[PWGCF/EbyE] Fixing process() and all the linters

[baasingh]

• Subscribe required table in the process function,
• To fix linters code name need to change.
• Fix all the linters which were not done in the previous: https://github.com/AliceO2Group/O2Physics/pull/14042

[github-actions]

O2 linter results: ❌ 0 errors, ⚠️ 2 warnings, 🔕 0 disabled

[vkucera]

@baasingh Don't open your PR as ready for review if it doesn't pass required checks.

[vkucera]

Why did you give the file a wrong name in 47c6de8?

[baasingh]

Hi @vkucera, thank you so much for the reply.
I was trying to fix all the linter issues, one of which was the code name, so II did this PR:
33a4c66
but it gave errors for other workflow names.

Now, i tried to revert back in this: 47c6de8

I am not able to comprehend the issue.

Thanks,
Balwan

[vkucera]

Which remaining issues are you trying to fix exactly?

[baasingh]

I was asked in my previous PR to fix the linter issues (https://github.com/AliceO2Group/O2Physics/pull/14042#pullrequestreview-3580503130)

Now, there is one left linter issue,
when I run the command:
python3 Scripts/o2_linter.py PWGCF/EbyEFluctuations/Tasks/FactorialMomentsTask.cxx
i get: PWGCF/EbyEFluctuations/Tasks/FactorialMomentsTask.cxx:1: warning: Use lowerCamelCase or UpperCamelCase for names of C++ files. See the O2 naming conventions for details. [name/file-cpp]

Results for failed, tolerated and disabled tests

[vkucera]

But that's the one you just introduced with your last commit.

[baasingh]

But that's the one you just introduced with your last commit.

Thank you for your help.

Just to clarify, I was trying to resolve the linter error related to the file name. I attempted changing it to lowercase, which is why I was encountering this issue.

Thanks again for your guidance.

[baasingh]

i am closing this PR and will open new one after rebasing my branch.

[vkucera]

i am closing this PR and will open new one after rebasing my branch.

Opening a new PR is completely useless and counterproductive. There is no reason why you could not update the same PR.

[baasingh]

i am closing this PR and will open new one after rebasing my branch.

Opening a new PR is completely useless and counterproductive. There is no reason why you could not update the same PR.

Hi, thank you for the message. I will take care in future.