Page MenuHomeSoftware Heritage
Create Task
Maniphest T3632

Investigate the ContentDisallowed exception
Closed, MigratedEdits Locked
Actions

Description

There seem to be trouble in the celery/rabbitmq communication with [1]

This impacts all modules using celery/rabbitmq (loader, lister, vault, ...) [2].
It does not seem to prevent the overall stack from running though.

[1] https://sentry.softwareheritage.org/share/issue/b3632f4f2c5c4f9a926f36c1fce4a906/

[2] sentry says at least 3k for each dvcs loaders and lister, 27k for the loader-core...

Revisions and Commits

rDSCH Scheduling utilities
AbandonedD6410 Allow application/x-msgpack deserialization again

Event Timeline

ardumont triaged this task as Normal priority.Oct 5 2021, 11:54 AM
ardumont created this task.
ardumont added a revision: D6410: Allow application/x-msgpack deserialization again.Oct 5 2021, 12:20 PM
douardda added a subscriber: douardda.Oct 8 2021, 3:06 PM

Unless I'm mistaken, this error does not appear in sentry any more, right?

ardumont added a comment.Oct 8 2021, 3:57 PM

maybe, yes.

Since i don't really see how to check that, I was in a mood to just mark it as
resolve in sentry until sentry shout "regression" (or not hopefully)

ardumont added a project: Scheduling utilities.Oct 8 2021, 4:08 PM
ardumont added a comment.Oct 8 2021, 4:20 PM

It still appears in sentry.
Although it seems specific to staging (which is a hint of a divergence of some sort).

another one: https://sentry.softwareheritage.org/share/issue/83b0793debee4abd9693cdb031993c7b/

douardda added a comment.Oct 11 2021, 12:15 PM

What's the difference in deployed dependencies versions (staging vs. prod)?

ardumont added a comment.EditedOct 15 2021, 11:52 AM

No difference.

I've made a pass on sentry and "resolved" the issue per project.
The oldest event was systematically 7 days old for each project occurrence.
Let's see if that happens again.

ardumont closed this task as Invalid.Oct 26 2021, 12:37 PM
ardumont claimed this task.

Sentry never reported any regression since it got marked as resolved.
So that issue was no longer relevant when i opened it, closing it as invalid.

gitlab-migration changed the task status from Invalid to Migrated.Jan 8 2023, 4:35 PM
gitlab-migration claimed this task.
gitlab-migration added a subscriber: gitlab-migration.

This task has been migrated to GitLab.

About · Developer information · Legal