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

Cannot declare bad PFNs #4265

Closed
dchristidis opened this issue Jan 25, 2021 · 0 comments · Fixed by #4270
Closed

Cannot declare bad PFNs #4265

dchristidis opened this issue Jan 25, 2021 · 0 comments · Fixed by #4270
Assignees
Milestone

Comments

@dchristidis
Copy link
Contributor

Motivation

We have identified another regression from the recent SQLAlchemy changes. In this part of the code, state can be BAD, but str(BadPFNStatus.BAD) evaluates to 'BadPFNStatus.BAD'.

Modification

Use BadPFNStatus.*.name instead.

@dchristidis dchristidis changed the title Cannot declare bad PNFs Cannot declare bad PFNs Jan 25, 2021
@dchristidis dchristidis assigned dchristidis and unassigned mlassnig Jan 25, 2021
dchristidis added a commit to dchristidis/rucio that referenced this issue Jan 25, 2021
This is a stopgap solution. It should be followed up in issue rucio#4269.
dchristidis added a commit to dchristidis/rucio that referenced this issue Jan 25, 2021
This is a stopgap solution. It should be followed up in issue rucio#4269.
bari12 added a commit that referenced this issue Jan 25, 2021
…permission_for_declaring_bad_PFNs

Core: Fix ATLAS permission for declaring bad PFNs #4265
bari12 pushed a commit that referenced this issue Jan 25, 2021
This is a stopgap solution. It should be followed up in issue #4269.
@bari12 bari12 added this to the 1.24.2 milestone Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants