In the end, it's not necessarily data [1] which is obsolete. It's more having
partial production dump mounted on staging. We have dangling data.

I've realigned the dbs already.

I completely missed the 2 still needed (added back in db)

@legau You can push if you want ;)
(I can do it otherwise)

closed by 2209d313b58626a1db6aa47b2a10bc5edb9b32f2

Wondering if there isn't a simpler implementation leveraging that field's upload_to after all [1]
(instead of modifying the system storage...)

The tests are failing. I recall there is a something on the model about filename in the deposit model... [1]

Rebase on latest master

That's my cue ;)

Rebase on latest master

lol at the description ;)

Thanks for the cleanup

Could my comment be implemented in a followup diff?

Nice!

(amended the db, yes it's already deployed even though not tagged)

"bravo encore une fois ardumont" :)

And thanks again for looking into it ;)

I've add multiple looks to the proposed gitea lister.
This looks fine to me, i've accepted it but not completely.
If some other team member could do a second pass, that'd be neat.

Well, looks fine to me.
I'm no gitea expert though so I'd like other team member to review as well.

Bump dep on attrs_strict >= 0.0.7
now it's on pypi.

(forgot to select)

Looks good ;)

Adapt according to review

Thanks for the flag \o/

I don't recall the flag needed to exclude the cassandra tests from the tox or pytest run.
That'd be great to add it in there somewhere i guess.

It gets all the more annoying when that popup hides the other visit.
As in the following, below the popup exists other visits we no longer can see.

Re-reading (and realizing again) the argument on metadata being phased out. So,
we can drop those unused [1] metadata field from origin-visit/origin-visit-status then.

I think we should do away with the metadata attributes completely.
I'm not sure why we added them to OriginVisitStatus in the end, instead of
removing them, after we checked that they were always empty in production
data.

That's been running since 15:30 or so.

D3176 landed, packaged, deployed.