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

messed up dataset names prevents caching of did lookups #759

Open
ivukotic opened this issue May 2, 2024 · 1 comment
Open

messed up dataset names prevents caching of did lookups #759

ivukotic opened this issue May 2, 2024 · 1 comment
Assignees

Comments

@ivukotic
Copy link
Member

ivukotic commented May 2, 2024

If I look at the postgresdb datasets, I see things like this:

 rucio://mc20_13TeV.364157.Sherpa_221_NNPDF30NNLO_Wmunu_MAXHTPTV0_70_CFilterBVeto.deriv.DAOD_PHYSLITE.e5340_s3681_r13145_p6026?files=1
 rucio://mc20_13TeV.364157.Sherpa_221_NNPDF30NNLO_Wmunu_MAXHTPTV0_70_CFilterBVeto.deriv.DAOD_PHYSLITE.e5340_s3681_r13145_p6026?files=2
 rucio://mc20_13TeV:mc20_13TeV.345705.Sherpa_222_NNPDF30NNLO_ggllll_0M4l130.deriv.DAOD_PHYSLITE.e6213_s3681_r13167_p6026?files=1```

each time we append something to the dataset name it will do a new did lookup and it will fail as there is no such dataset. 
I also find it not at all clean way to pass parameters.
@ivukotic
Copy link
Member Author

ivukotic commented May 9, 2024

this will be solved with #767

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

No branches or pull requests

3 participants