-
Notifications
You must be signed in to change notification settings - Fork 37
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
Add change dbs dataset file status fix #5204 #5241
Add change dbs dataset file status fix #5204 #5241
Conversation
I did a quick test on CMSSW_9 on lxplus7 (python2) and it is OK. Once have test in Jenkins will run all archs |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
thanks a lot @novicecpp |
@novicecpp I captured your comments before in this list of actions. I will add more as needed once you answer my questions. Feel free to check and comment in there. Thanks |
Maybe move HTTPRequests to utils and move DBSREST to new file same level as CrabRestInterface.py? |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Hope I addressed all coments (only the
|
This comment was marked as outdated.
This comment was marked as outdated.
code with last changes is now tagged as testSetDsetFilesStatus.2 in the ad-hoc test branch |
Jenkins results:
|
ooopppss. I had added content-type in the wrong place. But of course CRAB Server REST happily ignores it and everything kept working, but better not confuse the reader. |
If there are no more objection I will do a BIG SQUASH and merge. |
Jenkins results:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good now. Thanks.
thanks @mapellidario and @novicecpp for review and advice. I will merge. And we can discuss separately if/how to add --recursive. Maybe wait for someone to ask for it 😁 ? We still have time to decide if to keep old semantic (Invalidating a dataset will automatically invalidate all the files in the dataset) or leave it to user with two actions as I indicated above. It seems a soft decisions, with arguments in pro/con either choice. |
Since in current implementation |
Thanks Stefano for the detailed description of dataset and file validity in DBS. Sorry for the dumb questions! Do we already have an entry in the FAQs about DBS dataset and file status? Since we are allowing users to change it, we should also provide clear instructions about what those are and what the commands we provide do (or plan to do). |
Dario,your questions were not dumb. The problem is that there is no real rule on how to use those status flags, As user documentation this is what we have: |
Jenkins results:
|
4e5f421
to
348d546
Compare
Jenkins results:
|
I think this is OK now. Aside from